ethereum-optimism / ethereum-optimism/optimism

Automated Github Triaging

Open
#14,426 0 comments 0 reactions 1 assignee Claimed by @raffaele-oplabs View on GitHub
A-ops C-feature C-good first issue M-community S-exempt-stale T-platforms
Dominant language
Go
Stars
6.5k
Forks
4k
Avg merge
2d 15h
Merged PRs (30d)
145

Description

**Is your feature request related to a problem? Please describe.**

There isn't a defined triaging system for repo issues, and that would make it a poor experience for community participation.

**Describe the solution you'd like**
After a brief discussion with @ajsutton upong the suggestion from @mds1, we should implement an automated labelling system for new issues, based on an issue template. This is what Foundry does:

Issues are a form submission that has dropdowns, and based on what tool you choose (forge, cast, anvil) and the issue kind (bug, feature) [labels are automatically applied](https://github.com/foundry-rs/foundry/tree/master/.github/ISSUE_TEMPLATE):

Here are there [bug report](https://github.com/foundry-rs/foundry/issues/new?template=BUG-FORM.yml) and [feature request UIs](https://github.com/foundry-rs/foundry/issues/new?template=FEATURE-FORM.yml) to see how it works.

In our case, it would be ideal if the automated labelling would apply an A label, a T label, and maybe a couple C or M labels if they are easy to do.

Once issues are automatically triaged into pertaining to a team and area, it would be much easier for teams to keep a curated issue backlog.

**Describe alternatives you've considered**
- The current system, which is undefined, is not really great experience and just makes issues go unnoticed or stale.
- A company-wide rotation would make it very difficult for whoever is on call to accurately triage everything.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.