-
-
Notifications
You must be signed in to change notification settings - Fork 238
MAINT: auto assign workflows #214
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
Conversation
|
Great idea! Have you been able to test if these actions work? |
I've tested the auto-assingment for issues and pull requests and worked correctly. It assigns the author as assignee (for issues we could re-think that) and the reviewers of PRs are automatically me, giovani and Stano. For the projects assignment I was not able to test in another public repository. Had some in a private one earlier, but the worst case scenario is that that workflow doesn't work and therefore the issue/task is not added to the project. So in the end of the day would not be bad if it doesn't work on our first try. Anyway, once we discuss every detail, would you like to merge this before or after the 2022 hackathon? Take in mind that this will assign 3 people as reviewers for every PR, for instance. But of course we could modify the workflow to work properly during hackathon, we could do this in another fork |
|
@giovaniceotto @MateusStano @PatrickSampaioUSP , I'm asking review from one of you. Can we proceed with approving/merging? Everything should be working now. |
|
@PatrickSampaioUSP is better suited to review this one. I'll add him as soon as he accepts the invite to participate in this repo. |
|
Added @PatrickSampaioUSP as a reviewer. |
PatrickSampaioUSP
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good, we should merge it and test
|
Idk why but this not worked when Franz opened the last PR |
|
Still not working, right? |
Perfectly, not yet, but it already worked on some cases. For sure, the 'auto-assign to project' is definetely not working |

Pull request type
Please check the type of change your PR introduces:
Pull request checklist
Please check if your PR fulfills the following requirements, depending on the type of PR:
ReadMe, Docs and GitHub maintenance:
What is the new behavior?
I'm trying to add the following workflows to this setup
Does this introduce a breaking change?