Many bug reports are not about bugs (e.g. just hard to understand
behavior and so on) and some of the remaining are not about bugs in our
project.
It's up to the person doing bug triage to mark whether one believes this
is really a bug or no. Adding "bug" label to everything just introduces
noise.
This will make bug reports more structured, and easier for triagers and
maintainers to work with.
Signed-off-by: Dom Rodriguez <shymega@shymega.org.uk>
What the subject line says really. As per @walker0643's feedback, the
stale bot now encourages the author of the issue/PR to close it
themselves, if it is no longer an issue, or if they no longer want to
work on the PR.
Signed-off-by: Dom Rodriguez <shymega@shymega.org.uk>
This commit changes the configuration of the stale bot. It will now mark
issues as stale after 6 months. In days, this is 182(.5, if you want to
be super precise, but let's go with 182).
This should reduce the noise made by the bot.
Signed-off-by: Dom Rodriguez <shymega@shymega.org.uk>
This commit changes the configuration of the stale bot. It no longer
closes stale issues, and instead gives a friendly 'nudge' for stale
issues.
The next commit will change the time for issues to be marked stale to 6
months. This should help reduce the noise from the bot.
Signed-off-by: Dom Rodriguez <shymega@shymega.org.uk>
This commit fleshes out the messages and labels applied to stale
issuse/PRs, configures 'exempt' labels, and additionally the number of
days before a issue is marked stale/closed.
Signed-off-by: Dom Rodriguez <shymega@shymega.org.uk>
Our current templates do not use the latest GitHub templates, so this updates them. I have adjusted and removed some wording to make the template simpler, as I have found some users neglect to fill in the template, or partially fill it in. I hope this helps with the bug reporting process.
