Sync issue templates: record the kind as an issue type - #64
Merged
Conversation
Contributor
|
| Filename | Overview |
|---|---|
| .github/ISSUE_TEMPLATE/bug_report.yml | Adds the Bug issue type to the existing bug-report form without changing its labels, assignment, or fields. |
| .github/ISSUE_TEMPLATE/feature_request.yml | Adds the Enhancement issue type to the existing feature-request form without changing its labels, assignment, or fields. |
Reviews (5): Last reviewed commit: "Merge branch 'main' into chore/issue-typ..." | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Valgrind Memory Checks - PASSED%%{init: {'themeVariables': {'pie1': '#2da44e', 'pie2': '#cf222e'}}}%%
pie showData
title Test binaries under Valgrind (28 total)
"Clean" : 28
"Leaking" : 0
Full valgrind output (last 300 lines)A/B Benchmark Report - report-onlyOutput (last 300 lines)Commit |
DerekCorniello
force-pushed
the
chore/issue-types
branch
from
August 21, 2026 04:04
3fdcc9e to
1013f60
Compare
Contributor
Author
|
Updated: It only means invited to this repo, which can be read-only or triage-level, so it does not imply the ability to set priority and status. Removing The template-sync branches were also rebuilt from |
Every form now sets a type (Bug, Enhancement, Documentation, Chore or Decision), so kind is a first-class field rather than something inferred from which form was used and re-encoded as a label at triage. Synced from muxlang/.github/templates - not hand-edited. Part of muxlang/mux-context#19
DerekCorniello
force-pushed
the
chore/issue-types
branch
from
August 21, 2026 04:17
65b9a17 to
adcdff0
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Every form now sets an issue type - Bug, Enhancement, Documentation, Chore or Decision - so kind is a first-class field rather than something inferred from which form was used and then re-encoded as a label during triage.
The org types were created and all open issues backfilled; see muxlang/.github#8 for the source change and the full mapping.
Synced from
muxlang/.github/templates, not hand-edited.Part of muxlang/mux-context#19