Include type updates in bicep release notes/issues
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
It would be great if in our release notes we listed all the type updates that have happened between releases. Even once we start shipping type updates separate from core bicep, it would still be good to include the list of changes in those type updates.
What would also be cool is if we could auto-reply/auto-close any issues that have been filed against a specific type. I think we would need to be more methodical about labels in order to automate this.
Contributor guide
Research direction
Start by reviewing how Bicep release notes are produced and how issues are labeled, since the issue names neither files nor tests. Define the type-update information that must appear between releases, then determine how labels could support automatic replies or closure for type-specific issues.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, release, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100