Fix issue form labels to match repository labels - #42
Merged
Conversation
The issue forms declared `kind/documentation` and `kind/enhancement`, neither of which exists in this repository. GitHub silently ignores labels that do not exist, so issues created from either form were left unlabeled. Point both forms at labels the repository actually has: `documentation` for the documentation issue form and `enhancement` for the new content form.
Contributor
|
Looks good thank you |
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
2 participants
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.
Description
이슈 템플릿이 선언하고 있는
kind/documentation,kind/enhancement라벨이 저장소에 존재하지 않아, 템플릿으로 생성한 이슈에 라벨이 붙지 않고 있습니다. 저장소에 실제로 있는 라벨을 가리키도록 수정했습니다.documentation-issue.yamlkind/documentationdocumentationnew-content.yamlkind/enhancementenhancement#29에서 두 가지 해결 방법을 제시했는데, 그중 PR로 처리 가능한 쪽으로 작업했습니다.
kind/라벨을 새로 만드는 방향을 선호하신다면 이 PR은 닫고 라벨 생성으로 진행해 주셔도 됩니다.Type of change
Related issue
Fixes #29
Checklist
tox -e docstox -e pep8index.rsttoctree.heading levels,
한글(English)on first use of a term).Additional notes
이 변경은
.github/ISSUE_TEMPLATE의 YAML 2줄 수정이라 문서 빌드·린트에 영향이 없지만, 확인 차 로컬에서tox -e docs와tox -e pep8을 실행해 둘 다 통과했습니다. 새로 추가한 페이지가 없어 toctree 등록과 rST 규칙 항목은 해당하지 않아 비워 두었습니다.