microsoft / microsoft/vscode-azurestaticwebapps
Detect and pre-fill settings for popular frameworks by analyzing the workspace
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 99
- Forks
- 39
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 2
Description
Related to #277
In an effort to improve the success rate of the first GitHub Action run after creating a new static web app, we want to be able to intelligently pre-fill these options based on the users' workspace.
What we want to detect (for GH action workflow):
- Build output location
- Source code location
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
The payload names no files or tests; begin by reading related issue #277 and tracing the extension's workspace analysis and GitHub Actions workflow creation entry points. Clarify which popular frameworks and workspace signals are in scope, with completion defined as pre-filling source-code and build-output locations for supported workspaces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, github-actions, typescript, vscode
- Domain
- ci-cd, cloud, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100