-
Notifications
You must be signed in to change notification settings - Fork 57
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
Add Issue/PR the Project, when assigned to a milestone? #26
Comments
Did I understand correctly that you are looking for a way to add issues to a project board when they are added to a milestone? If so, this is definitely not possible right now, the only way to add issues is via In theory it would be possible to create an "add issue to board when it is added to milestone Can you tell a bit more about the use case behind that? Do you want one project board per milestone? |
That is correct.
Yes. Right now, the projects are milestone-based - one project board for 2.7, one for 2.8, one for 2.9, etc. |
Can you think of a name for the "trigger" that would somehow match the current scheme? This might be the biggest hurdle right now. |
I've not looked at the logic, but could (Aside: there's no If not, maybe |
Reusing doesn't work, something has to tell the code that it should add an issue. So But: This of course opens the possibility of further "triggers" to add an issue or PR to a board. Any other useful ones?
Seems so. Best create an issue for it. |
+1 for this - I'd love a way to automatically add a PR or Issue to a project when it is added to a milestone, and the inverse, it'd be great to remove it from the project automatically when it is removed from that milestone. Something like:
|
Note that the current implementation only moves already existing items and does not add them to a board. That's why implementing this would be a major new feature for the bot and would probably require a rework on the naming of stuff. |
I would like this feature |
+1 |
Would it be possible to add functionality, such that Issues and PRs assigned to X milestone get put in X project (and then existing rules could presumably automatically put that in a particular column.)?
Right now, the readme suggests that
milestoned_issue
can only be used to move a card once it has already been added.What we don't want is to require that all issues automatically get added to a project.
The text was updated successfully, but these errors were encountered: