-
Notifications
You must be signed in to change notification settings - Fork 2
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 automation to close sprint boards x days after the sprint is over #6
Comments
Changing the status of a project depends on PyGithub/PyGithub#1817 |
larsks
added a commit
to larsks/sprint-tools
that referenced
this issue
Jan 7, 2021
This will close sprint boards 28 days after they were created. Closes CCI-MOC#6
larsks
added a commit
to larsks/sprint-tools
that referenced
this issue
Jan 7, 2021
This will close sprint boards 28 days after they were created. Closes CCI-MOC#6
larsks
added a commit
to larsks/sprint-tools
that referenced
this issue
Jan 7, 2021
This will close sprint boards 28 days after they were created. Closes CCI-MOC#6
larsks
added a commit
to larsks/sprint-tools
that referenced
this issue
Jan 7, 2021
This will close sprint boards 28 days after they were created. Closes CCI-MOC#6
larsks
added a commit
to larsks/sprint-tools
that referenced
this issue
Jan 8, 2021
This will close sprint boards 28 days after they were created. Closes CCI-MOC#6
larsks
added a commit
to larsks/sprint-tools
that referenced
this issue
Jan 8, 2021
This will close sprint boards 28 days after they were created. Closes CCI-MOC#6
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This sounds simple but might be tricky; how do we know -- programatically -- when a sprint is over?
The text was updated successfully, but these errors were encountered: