Azure / Azure/Azure-Verified-Modules
[Documentation Update]: Bicep contribution guidelines - how to enforce locations in deployment tests
Open
Language: Bicep :muscle:
Needs: Core Team :genie:
Status: In Triage :mag:
Type: Documentation :page_facing_up:
- Dominant language
- PowerShell
- Stars
- 580
- Forks
- 161
- Avg merge
- 11h 3m
- Merged PRs (30d)
- 15
Description
### Check for previous/existing GitHub issues
- [x] I have checked for previous/existing GitHub issues
### Description
Document how to enforce locations in deployment tests via the `enforcedLocation` parameter and not via the gh workflow
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Bicep contribution guidelines and the deployment-test documentation. Document how to enforce locations with the `enforcedLocation` parameter rather than through the GitHub workflow; the update is complete when contributors can follow that guidance for deployment tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100