You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 10, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: