-
Notifications
You must be signed in to change notification settings - Fork 1
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
Move to column in the absence of a label #1
Comments
Thanks for your feedback! Here's my take on your suggestions:
I'll start working on the label removal feature. Feel free to open new issues for any other ideas! |
Does this sum up the overall desired flow for your specific use cases?
|
We solved this with assign-issue-action. This action adds a label, which is then processed by the github-action-move-issues. |
Quite. The start should be "Issue labeled" (instead of "New issue") The label is coming mostly when a student writes "Can I get assigned" and then we assign that label. For more advanced workflows: The student issues |
This should provide you with the functionality you want: #7 |
In our project, we use the label
FirstTimeContribution
to indicate that a student was assigned and starts working on an issue. Then, we move the issue from "Free to take" to "Assigned". - If a student becomes inactive, we remove the label "FirstTimeContribution". Then, we also want the issue be moved back to "Free to take". - This currently seems to not supported by the action, but we would really like to see it.It woudl be also nice if there was a sync between the field "Assignees" (empty or non-empty) and columns. But this seems to be out of scope of this project?
In case a pull reuqest is submitted referencing an issue, the issue should be moved from "Assigned" to "In Progress". Would such a feature be in-scope of this project? Then, I can file a separate issue for it.
The text was updated successfully, but these errors were encountered: