Azure / Azure/bicep-registry-modules
[AVM Question/Feedback]: Git Hooks for contributing QoL
- Dominant language
- Bicep
- Stars
- 736
- Forks
- 564
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 30
Description
### Check for previous/existing GitHub issues
- [X] I have checked for previous/existing GitHub issues
### Description
When I'm contributing, I tend to forget to run Set-AVMModule when pushing changes. Which I realize after the validation has run in the testing pipelines.
To improve QoL of contributing to AVM it might worth checking [git hooks](https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks). For example there can be a pre-commit git hook which runs the same script as in the CI to check if Set-AVMModule has run. The contributor gets this feedback instantly when trying to commit, instead after committing, pushing, running the pipeline etc.
Contributor guide
Research direction
Start by locating the CI validation that checks whether Set-AVMModule has run, then review how this repository handles contributor tooling and Git hooks. Done means contributors receive the equivalent check before committing, with the existing CI validation still covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100