ADR-003 Use Single-Process Approach for Architecture Requests + Issue templates #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add GitHub Issue Templates and Labels
Summary
This PR adds GitHub integration to make it easy for people to ask architecture questions:
architecture-questionProposed Labels
I suggest we create these labels manually after merging:
Core Labels (Required)
architecture-question#0E8A16(green)high-impact#D93F0B(red)urgent#B60205(dark red)adr-needed#5319E7(purple)Optional Status Labels
needs-decision#FBCA04(yellow)waiting-for-feedback#FEF2C0(light yellow)resolved#0E8A16(green)Optional Category Labels
integration#1D76DB(blue)standards#1D76DB(blue)security#D93F0B(red)infrastructure#BFD4F2(light blue)Discussion question: Should we start with just the 4 core labels and add more as needed? Or create the full set upfront?
Blank Issues: Enabled ✅
Set to
trueto lower barrier. Anyone can open issue without template.Rationale: Better to be welcoming than strict. We can require templates later if needed.
Question: Agree, or should we require template usage?
Discussion Questions for Reviewers