Bug fix: Deployment not tracked against PR branch when using appVersion: PR_<ID>#2136
Draft
spetersenms wants to merge 11 commits intomicrosoft:mainfrom
Draft
Bug fix: Deployment not tracked against PR branch when using appVersion: PR_<ID>#2136spetersenms wants to merge 11 commits intomicrosoft:mainfrom
spetersenms wants to merge 11 commits intomicrosoft:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
❔What, Why & How
When using Publish to Environment and setting the version to a PR branch, the deployment itself will work, however the deployment entry in Github will show a deployment against the main branch. This happens since the workflow runs against the main branch and downloads the PR artifacts.
This feature adds another step after a successful deployment from a PR that deactivates the deployment entry created by GitHub and creates a new manual one against the PR branch/ref.
This gives a better overview in the deployment UI and makes it easier to understand where a deployment actually came from.
Related to issue: #2118
✅ Checklist