Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Sprint automation: when a PR links to an issue, move the issue across the sprint board with the PR #652

Closed
mbestavros opened this issue Jun 29, 2020 · 1 comment
Closed

Sprint automation: when a PR links to an issue, move the issue across the sprint board with the PR #652

mbestavros opened this issue Jun 29, 2020 · 1 comment
Assignees
@mbestavros
Labels
infrastructure General issues around project infrastructure

Comments

@mbestavros
Copy link
Contributor

mbestavros commented Jun 29, 2020 •
edited
Loading

The Enarx sprint framework treats pull requests differently from issues: they have their own workflow for being reviewed and merged.

Pull requests frequently link to issues in order to automatically close them. However, this means that when a PR is added to the sprint board in order to track its progress, the task encapsulated by its linked issue is duplicated (both the issue and the linked PR are present, when they refer to the same task).

To minimize this duplication, we should have issues move alongside PRs when they are linked.
@mbestavros mbestavros added the infrastructure General issues around project infrastructure label Jun 29, 2020
@mbestavros mbestavros changed the title Sprint automation: when a PR links to an issue, move the issue across the sprint board instead of the PR Sprint automation: when a PR links to an issue, move the issue across the sprint board with the PR Jul 16, 2020
@mbestavros mbestavros self-assigned this Jul 16, 2020
@mbestavros
Copy link
Contributor Author

Moved here: enarx-archive/bot#13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mbestavros mbestavros

Labels
infrastructure General issues around project infrastructure
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mbestavros