fix(issue-templates): declare native issue type on each template#49
Open
fix(issue-templates): declare native issue type on each template#49
Conversation
Adiciona campo `type:` em cada template para que o GitHub aplique o Native Issue Type automaticamente ao criar a issue via UI — alinhado com os tipos configurados na org `nfe` (organization.issueTypes via GraphQL). Mapeamento: feature.yml -> type: Feature bug.yml -> type: Bug improvement.yml -> type: Improvement spike.yml -> type: Spike docs.yml -> type: Docs chore.yml -> type: Task (name e 'Chore / Task') incident.yml -> type: Incident Antes desta mudanca, os templates declaravam apenas `name:` e `description:`. Issues criadas via UI ficavam com `type=null` ate intervencao manual ou ferramenta externa setar via REST PATCH. A skill `nfe:create-issue` em `nfe/skills-internal` ja cobria chamando set_native_type.sh apos create_issue, mas o caminho UI ficava descoberto. Com `type:` declarado, ambos os caminhos (UI e skill) produzem issue com Native Type aplicado de origem. Verificacao da org: todos os 7 Native Types (Feature, Bug, Improvement, Spike, Docs, Task, Incident) estao habilitados em `nfe` com `isEnabled=true`. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Resumo
Adiciona campo
type:em cada um dos 7 templates de issue em.github/ISSUE_TEMPLATE/para que o GitHub aplique automaticamente o Native Issue Type correspondente quando o usuario criar uma issue via UI.Motivacao
Antes desta PR, os templates declaravam apenas
name:edescription:. Issues criadas via UI ficavam comtype=nullna entidade GitHub Issue — exigindo intervencao manual (UI seleciona Type explicitamente) ou ferramenta externa que faca PATCH via REST API depois.A skill
nfe:create-issue(emnfe/skills-internal) ja contornava isso chamandoscripts/set_native_type.sh(REST PATCH) aposcreate_issue, mas o caminho UI nativo do GitHub ficava descoberto. Resultado: backlog ficava com mistura de issues com e sem Native Type, confundindo views/filtros do Project nfe/5.Com
type:declarado no template, ambos os caminhos (UI direta e skill) produzem issues com Native Type aplicado de origem — sem dependencia de pos-processamento.Mapeamento aplicado
name(existente)type(novo)feature.ymlFeatureFeaturebug.ymlBugBugimprovement.ymlImprovementImprovementspike.ymlSpikeSpikedocs.ymlDocsDocschore.ymlChore / TaskTaskincident.ymlIncidentIncidentPara
chore.yml, onamepermaneceChore / Task(descritivo), mas otypemapeia paraTask— Native Type configurado na org.Verificacao da org
Confirmado via GraphQL
organization(login:\"nfe\"){issueTypes{nodes{name isEnabled}}}que todos os 7 Native Types estao habilitados emnfe:Task(isEnabled=true)Bug(isEnabled=true)Feature(isEnabled=true)Improvement(isEnabled=true)Spike(isEnabled=true)Docs(isEnabled=true)Incident(isEnabled=true)Cross-repo
PR complementar em
nfe/skills-internal(PR #25, branchfeat/create-issue-ux-rework) ja aplica o mesmo fix nos placeholdersassets/issue-templates/*.ymlda skillnfe:create-issue. Isso garante que repos onde a skill faz bootstrap (Etapa 1c) recebam templates comtype:ja na publicacao — fechando o gap mesmo antes do sync diario do provisioner emnfe/.github#20.Test plan
nfe/skills-internal(ou outro repo da org) usando o templatebug.ymlvia UI — validar queissue.type.name == 'Bug'no payload retornado pela API.feature.ymlechore.yml(este ultimo deve resultar emtype.name == 'Task', naoTask / Chore).🤖 Generated with Claude Code