microsoft / microsoft/vscode-azurestaticwebapps
Add support for SWAs that are not linked to a remote repository
Open
Nobody has claimed this yet.
feature
- Dominant language
- TypeScript
- Stars
- 99
- Forks
- 39
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 2
Description
This most commonly occurs when a SWA is created/deployed via zipdeploy in the SWA CLI.
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
Start by reproducing an SWA created or deployed through zipdeploy in the SWA CLI, without a linked remote repository. Trace how the VS Code extension discovers and handles that SWA, then define the expected behavior and verify that such resources are supported without requiring a remote repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript, vscode
- Domain
- cloud, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100