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
Experiencing problems? Have you tried our Stack Exchange first?
This is not a support question.
Motivation
When going through our history of PRs, there is not an obvious way to figure out if a PR is included in a past, present, or future release, and what specific release version.
The change log allows us to go from a specific release, to the PRs, but basically we are missing the other direction.
Request
We can take advantage of some bots / automation, along with existing GitHub primitives to improve this story.
For example, each Release could create either a new "project" or "milestone" category inside of GitHub, with the release version number.
Then some automation could place PRs into those projects, allowing people to track the progress.
Then when a release is being baked, or actually released, you can simply see that project category shift from "will include" to "included".
This can also work across multiple releases and patches, where simply we associate the PR with all the relevant release projects/milestones, and just track its inclusion.
After this, we should be able to navigate to any PR, and from there, see which releases it is included (or will be included) in.
Solution
build automation to execute this process as a part of the release pipeline.
Are you willing to help with this request?
No.
The text was updated successfully, but these errors were encountered:
Is there an existing issue?
Experiencing problems? Have you tried our Stack Exchange first?
Motivation
When going through our history of PRs, there is not an obvious way to figure out if a PR is included in a past, present, or future release, and what specific release version.
The change log allows us to go from a specific release, to the PRs, but basically we are missing the other direction.
Request
We can take advantage of some bots / automation, along with existing GitHub primitives to improve this story.
For example, each Release could create either a new "project" or "milestone" category inside of GitHub, with the release version number.
Then some automation could place PRs into those projects, allowing people to track the progress.
Then when a release is being baked, or actually released, you can simply see that project category shift from "will include" to "included".
This can also work across multiple releases and patches, where simply we associate the PR with all the relevant release projects/milestones, and just track its inclusion.
After this, we should be able to navigate to any PR, and from there, see which releases it is included (or will be included) in.
Solution
build automation to execute this process as a part of the release pipeline.
Are you willing to help with this request?
No.
The text was updated successfully, but these errors were encountered: