Menu
Getting a flood of the same issues posted after an os upgrade broke something and no current solution at the moment and people are skipping past the readme page. Is there a way to create a sticky at the top of the Issues page of a github issues page to reduce the influx of duplicate reports?
578
Under your repository name, click Pull requests. In the list of pull requests, click the pull request that you'd like to link to an issue. In the right sidebar, in the "Development" section click . Click the issue you want to link to the pull request.
You just need to include #xxx in your commit message to reference an issue without closing it. With the new GitHub issues 2.0, you can use these synonyms to reference an issue and close it (in your commit message).
To link related issues in the same repository, you can type # followed by part of the issue title and then clicking the issue that you want to link. To communicate responsibility, you can assign issues. If you find yourself frequently typing the same comment, you can use saved replies.
Anyone can close an issue they opened. Repository owners, collaborators on repositories owned by a personal account, and people with triage permissions or greater on repositories owned by an organization can close issues opened by others.
Github has no good solution to this. If you create a CONTRIBUTING.md then github will display a banner on the "new issue" page suggesting that the reporter reads it, but unfortunately if they're already on that page they're unlikely to read it.
I'd suggest proactively reaching out to your community - forums, email, twitter, blog, reddit, whatever will reach them.
Other than that you'll just have to close a bunch of tickets as duplicates. It will help to have one very detailed ticket with information for people to refer to when you close them.
This is based on my experience with a somewhat large project in a similar situation.
86
It's a good practice to write an instruction about "The right way to report a bug". It should explain users how to search for an existing issue before creating a new one. A link is then put to the top of readme and on the wiki home page. (example 1, example 2)
As for sticky issues - no way.
44
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
