microsoft / microsoft/vscode-azureresourcegroups
[CoR] Deployment stage remains "Current" after successful deployment completion
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 78
- Forks
- 55
- Avg merge
- 16h 49m
- Merged PRs (30d)
- 139
Description
OS: Win11 x64
VS Code Insider: 1.132.0-insider
Build Version: 0.12.7-alpha.0
Regression: Not a regression
Repro Steps:
- Create a project using Copilot
- Select Deploy to Azure
- Complete the deployment workflow
Expect:
After deployment completes successfully, the Deployment stage is marked as Completed
Actual:
Deployment completes successfully, but the Deployment stage remains "Current".
More Info:
- Copilot reports:
Your portfolio site is deployed and live at: https://blue-glacier-099ff7b0f.7.azurestaticapps.net/
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by tracing the Deploy to Azure workflow used after creating a Copilot project, then reproduce the successful deployment and inspect where the Deployment stage changes state. Done means a successful deployment marks the stage as Completed rather than leaving it Current.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript, vscode
- Domain
- cloud, devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100