-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project board / issue / PR automation #13615
Comments
Two more issues that are related to automating PRs, though IMO not enough to be a part of the list above: |
@r0qs Update regarding (2). Before we can start closing stale issues, we need to deal with closing very old issues from the backlog. As discussed with @NunoFilipeSantos, we're going to do this via our board automation. So let's repurpose #13672 for this. Later, when we're done with closing the backlog, we'll turn it into actual stale issue bot. Here's my proposal on how to do this:
|
This is a bit overengineered for what we discussed. Rodrigo can do better things with his time. 😅 So before developing, let’s have a quick talk and refine it a bit. |
Replaces #8969 as the catch-all issue for board automation.
There have been a lot of ideas flying around related to boards so I thought I'd gather them in a single issue. Ultimately we may want to split it into smaller issues if some parts turn out to require significantly more effort but I think most of these will be fairly easy and the biggest bottleneck here is making decisions about what exactly we want and how to achieve it. For this a single list is easier to manage and update.
Triage
column on the board (https://github.com/ethereum/solidity/blob/develop/.github/workflows/triage.yml). Note: It only works for project boards at repository level (i.e. GH Project Classic).needs design
goes to design backlog.needs design
goes to implementation backlog.takeover
label to theTakeover
column on the focus board. Add removing them when the label is removed.external contribution
label for PRs submitted from people not in the Solidity team.has-dependencies
label for PRs or issues that have "Depends on #<PR/issue number>".documentation
label for PRs touching only files insidedocs/
,README
s and maybe a few other docs files we have.testing
if the PR only touches tests.optimizer
if the PR only touches optimizer source.The text was updated successfully, but these errors were encountered: