-
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
Implement project board automation #8969
Comments
For adding newly opened issues to "new issues", I think there is already automation which moves all new issues in "Solidity" project to "new issues". We just need to find a way to move newly created issues to "Solidity" project |
Looks like github docs have some ready to use examples for these:
Looks like they actually rely on third-party github actions. Also one more idea for what we could do: assigning triage issues (and maybe PRs to review) to random team members. The assigned person has to either deal with it or give it to someone else, but has to do something. |
Another idea: adding PRs labeled |
@r0qs We talked with @ekpyron today about next steps here.
|
I cleared the column an renamed it (actually deleted it and created a new one). Also, I have an idea for how we can work around the board not being able to handle solc-js issues. We could just add notes with links. Not great but better than not being able to manage them at all. |
As for new boards, looks like PAT seems to be the only way forward and we do want to move on to them if only because github is very likely to deprecate old ones at some point. So once devops creates a custom account for us, we could move on with that. |
I made a simple workflow to move new issues to triage in the old project board: #13528 I saw that you created a
Yes, using a PAT with organization permission to the |
Just a temporary place for me and @ekpyron to keep track of which old issues we have already labeled. For the purpose of this issue you can just ignore it. |
Just renamed it to avoid confusion with the triage column. |
We'll probably want to close this in favor of #13615. |
Closing in favor of #13615 |
Implement automation (maybe through github actions) for the following:
The text was updated successfully, but these errors were encountered: