Fix publishprofile workflow - #567
Closed
Akshay Kumar (kumaraksh1) wants to merge 8 commits into
Closed
Conversation
Akshay Kumar (kumaraksh1)
requested review from
Sarthak Sharma (sarsharma) and
Surender Singh Malik (surenderssm)
as code owners
August 14, 2026 08:19
Akshay Kumar (kumaraksh1)
requested a deployment
to
automation test
August 14, 2026 08:19 — with 
GitHub Actions
Waiting
GitHub Actions
Waiting
Akshay Kumar (kumaraksh1)
had a problem deploying
to
automation test
August 14, 2026 12:06 — with
GitHub Actions
Error
GitHub Actions
Error
Akshay Kumar (kumaraksh1)
temporarily deployed
to
automation test
August 14, 2026 12:09 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
Shilpi Rachna (ShilpiRach)
left a comment
Shilpi Rachna (ShilpiRach)
left a comment
There was a problem hiding this comment.
Please update the PR description that this would mean this workflow cannot be used to test while submitting a PR.
Also, do we have any doc / readme that tells how to test one's PR. If yes, let's update there
Shilpi Rachna (ShilpiRach)
approved these changes
Aug 17, 2026
Sarthak Sharma (sarsharma)
approved these changes
Aug 17, 2026
Akshay Kumar (kumaraksh1)
force-pushed
the
users/kumaraksh/fix-publishprofile-workflow
branch
from
August 17, 2026 10:04
76722e7 to
a674db3
Compare
Akshay Kumar (kumaraksh1)
requested a deployment
to
automation test
August 17, 2026 10:04 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
Akshay Kumar (kumaraksh1)
requested a deployment
to
automation test
August 17, 2026 10:08 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
Akshay Kumar (kumaraksh1)
requested a deployment
to
automation test
August 17, 2026 10:12 — with
GitHub Actions
Waiting
GitHub Actions
Waiting
Merged
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
3 participants
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.
Separating untrusted PR validation from credentialed deployment to prevent PR-controlled
With the new design, the PR validates that the action builds successfully, but it does not validate an actual Azure deployment before merge.
The validation flow is now:
PR opened
→ npm ci
→ npm run package
→ no credentials and no deployment
PR merged to master/releases/*
→ trusted push workflow runs
→ Azure/ACR authentication
→ builds action from merged commit
→ deploys to the test Web App