Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitMate Labelled Closed Issues Tonight #23

Open
sils opened this issue Dec 21, 2017 · 1 comment
Open

GitMate Labelled Closed Issues Tonight #23

sils opened this issue Dec 21, 2017 · 1 comment

Comments

@sils
Copy link

sils commented Dec 21, 2017

Hi everyone :)

TLDR: GitMate.io acted on closed issues (and PRs) unneededly tonight, likely on your repo. The issue is fixed now and we're improving QA. More info at https://gitlab.com/gitmate/open-source/gitmate-2/issues/275.

You're getting this email because you have been affected by a bug in GitMate.io this night and you're using the feature that was buggy.

In short: GitMate's stale rules acted on closed issues and PRs. That might have been comments like "this issue will be closed now because it's inactive" or the addition of stale labels on already closed issues.

We are sorry that this happened and fixed the problem as soon as we were aware. We are also introducing new measures to improve our stability with a new QA stage in addition to our existing ones so those kinds of issues don't happen again.

Please let us know if you would like to get a script to revert those actions; it seems though as most communities would rather keep it than sending out additional notifications.

We've summarized the incident at https://gitlab.com/gitmate/open-source/gitmate-2/issues/275 .

Please reach out to us if you have any further questions about this.

Sincerely,

Lasse Schuirmann

[email protected]
Founder of http://coala.io/, http://viperdev.io/ and http://gitmate.io/

@swashata
Copy link
Owner

GitMate.io thinks the label prediction failed because there are not enough labels. Three labels must have been set on at least three issues each.

The contributor prediction failed because there are not enough contributors. Three contributors must have authored comments on at least three issues each.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants