Stale labels were added to peoples repositories

What happened?

The Gist of It

• Stale labels were added to closed issues and PRs.
• Comments were done on closed issues.

Timeline

All times are UTC+1.

Dec 20

• 19:04: https://gitter.im/GitMateIO/support?at=5a3aa63cba39a53f1a8423a7
• 19:19: #271 (closed) is reported by @nkprince007 but nobody else is around
• 23:01: Upstream fix proposed by @nkprince007 (IGitt!191 (merged))

Dec 21

• 07:00: coala reported that closed issues are getting labelled stale
• 08:06: @sils wakes up
• 08:14: Upstream fix merged (IGitt!191 (merged)) and released
• 08:34: Initial fix merged (!413 (merged)) it is determined that the bug will not occur again until
• 09:34: Initial fix is released
• 09:50: ownCloud reports the issue #273 (closed)
• 09:56: @sils notices this affects the EE reaper plugin too and proposes !414 (merged) (together with upstream changes which are pulled in there)
• 10:06: !414 (merged) is merged

Who is affected?

There are 19 repositories affected. One of those on GitLab, 18 on GitHub.

The concrete list is confidencial since it reveals the existence of private repositories.

What has happened to solve this?

Related Issues

• #273 (closed)
• #271 (closed)

Fixes

• IGitt!191 (merged) (upstream)
• !413 (merged) (downstream, hotfix)
• !414 (merged) (downstream EE modules, hotfix)
• !415 (merged) (downstream regression tests)

Damage Control

Some projects reached out to us:

• https://github.com/owncloud/core/issues/29944#issuecomment-353307238
• https://gitter.im/coala/coala/maintainers (private)

We should reach out to affected users:

• TODO: Reach out to all affected users by email.

Correcting Repository State

Write a script that allows users to remove the labels and comments using GitHub events API.

not needed nobody wants this

Preventing Similar Issues in the Future

• TODO: Add release candidate stage to deployment (in addition to production and master/nightly)