Triaging GitHub Issues
On the Gatsby core team, we’ve found patterns that help us effectively triage incoming Github issues, providing answers to the community’s questions, identifying bugs, and providing contribution opportunities. Triaging issues is a great way to contribute to the Gatsby community and share your knowledge, without necessarily requiring a lot of deep context about the way the Gatsby codebase works.
We want to share these patterns with the broader community, so that if you’re interesting in helping us triage, you’re able to do so more effectively!
In this document we’ll answer common questions, list guidelines and illustrate a decision tree.
For Gatsby the first line of communication between a user and the team is the issue tracker on GitHub. Typically, every day 20-30 issues are opened — that’s one every hour!
An opened issue could be:
- a question that can be answered immediately
- a bug report
- a request for a feature
- or a discussion on a complicated use case
As a first touch maintainer, you might sift through, triage, communicate and manage this first line of communication.
You will typically:
- answer questions that can be answered immediately
- test and reproduce possible bug reports and label them appropriately
- communicate feature requests to the rest of the team and ensure a valid response
- enable discussions on complicated use cases, whether themselves or via the rest of team
We do first touch maintenance so that:
- Questions are answered swiftly and correctly, therefore making users happy
- Bug reports are reproducible and the most relevant data is collected before someone jumps in with a fix
- Unrelated issues are resolved promptly so we don’t spend too much time on them
Gatsby is unique among most open source projects because:
- Gatsby integrates with many third party tools (WordPress, Drupal, Contentful etc) via source plugins and hence the typical scope of issues is widened significantly
- Gatsby aims to be really beginner friendly (we want to be the new way someone gets started with web development) and this means that we need to accommodate a wide range of skill levels
- At Gatsby, we’ve defined a couple of metrics that we measure to ensure we’re responsive and helpful to our open source community
- Be empathetic. The author of an issue might be asking something that’s obvious to you but that doesn’t mean it’s obvious to them - it’s important to consider the issue from the author’s viewpoint. People often remember how you make them feel, not what you told them.
- Add context. When answering an issue, it can be useful to link to existing documentation, issues, PRs, or provide related context. This means the issue can serve as a reference to future readers.
- Encourage community contributions. Getting people involved makes a huge impact. It’s often worth spending the time to write up a task as a
good first issueinstead of fixing the issue yourself. This can provide a low friction way for someone to get more involved in open source!
- Give issue authors time to close their own issues. Sometimes, it might feel like an issue is resolved but the author could have follow up questions. It’s usually best to give them a day or two to close the issue themselves.
Labeling helps group issues into manageable sets and also improves searchability and scannability. We have a set of labels that we use to group issues based on their type and status. While we want to limit adding too many labels, feel free to add one if it seems relevant and helps with this grouping!
It’s nice to update labels as the state of an issue changes or if the type of an issue changes, for example if a question becomes a feature request. This means labels are transient in nature and subject to being updated as progress is made on addressing issues.
Check out the docs on issue labeling for more info
The resolution flowchart provides a decision tree for how issues should be categorized into one of five types: question or discussion, bug report, feature request, documentation, or maintenance.
Gatsby team members have saved certain common form responses to help accelerate issue triage.
We have a bot that helps us automate some aspects:
- Issues with a question mark in their title or starting with “how” are automatically labeled as questions
- Issues with an empty body are closed
- Issues with no activity are marked stale after 20 days. They are then closed after another 10 days unless there are additional comments or the “not stale” label is applied
When do I do a demo for an issue?
When a feature or pattern is not documented, it may be nice to make a demo to add clarity for the author and help future readers as well.
How do I reproduce a bug?
Every bug report should provide details on how to reproduce the bug. This is so important that there’s dedicated documentation on how to create good bug reproductions. Encourage issue authors to describe exactly how to reproduce a bug.
How much time do I spend on an issue?
Some issues might need more time than others and there isn’t any hard and fast rule. However, it’s best to spend time on an issue after the relevant info and reproduction is available.
Do I have to look at Discord?
You don’t have to. Some of us are active on Discord and you can be too if you like.
Do I use the same issue to track documentation additions or open a new one?
If the issue describes the context well enough, then it is okay to update its title and use the same issue to track the addition of relevant documentation.
When do I follow up on an issue?
If an author hasn’t responded to a comment for a week or two, it might be nice to follow up and ask if there’s anything else we can do to help. If the issue goes stale after that, our bot should be able to clean it up.
What do I do if an issue relates to something upstream?
It’s a good practice to open an issue in the upstream repository in cases like this but isn’t strictly necessary. Upstream in this case refers to repositories that house dependencies for Gatsby.
Edit this page on GitHub