// Create a user-facing GitHub issue from a PR, separating the WHAT from the HOW, with correct milestone, project, labels, and issue type.
| name | gh-issue-from-pr |
| description | Create a user-facing GitHub issue from a PR, separating the WHAT from the HOW, with correct milestone, project, labels, and issue type. |
Create a GitHub issue that captures the WHAT (user-facing feature or bug) from an existing PR that describes the HOW (implementation). Used when the project board needs an issue as the primary changelog/release unit.
gh CLI authenticated (gh auth status)gh pr view <PR_NUMBER> --repo penpot/penpot \
--json title,body,author,labels,baseRefName,mergedAt,state,milestone
Identify:
| Field | Source | Rule |
|---|---|---|
| Title | PR title | Rewrite from user perspective. Strip leading emoji prefixes (:bug:, :sparkles:, :tada:). Focus on observable behavior. Use imperative mood. |
| Labels | PR labels | Copy user-facing labels (bug, enhancement, community contribution). Skip workflow labels (backport candidate, team-qa). |
| Milestone | PR milestone | Always copy what's on the PR. Fetch with: gh pr view <PR_NUMBER> --json milestone --jq '.milestone.title' If the PR has no milestone, create the issue without one. |
| Project | Always Main | Penpot uses the Main project (number 8) for all issues. |
| Body | PR's user-facing section | Extract steps to reproduce or feature description. Omit internal details. Use templates below. |
| Issue Type | PR labels / title | Map: bug label or :bug: title ā Bug. enhancement label or :sparkles: title ā Enhancement. Feature/epic ā Feature. Default ā Task. |
Bug template:
### Description
<what breaks, what the user experiences>
### Steps to reproduce
1. <step 1>
2. <step 2>
### Expected behavior
<what should happen instead>
### Affected versions
<version>
Enhancement template:
### Description
<what the user can now do that they couldn't before>
### Use case
<why this is useful, who benefits>
### Affected versions
<version>
Write the body to a temp file to avoid shell quoting issues:
cat > /tmp/issue-body.md << 'ISSUE_BODY'
<body content here>
ISSUE_BODY
Create:
gh issue create \
--repo penpot/penpot \
--title "<Title>" \
--label "<label1>" \
--label "<label2>" \
--milestone "<milestone>" \
--project "Main" \
--body-file /tmp/issue-body.md
Output: https://github.com/penpot/penpot/issues/<NUMBER>
Assign the issue to the PR author so they're responsible for it:
AUTHOR=$(gh pr view <PR_NUMBER> --repo penpot/penpot --json author --jq '.author.login')
gh issue edit <ISSUE_NUMBER> --repo penpot/penpot --add-assignee "$AUTHOR"
gh issue create can't set the Issue Type directly. Use GraphQL.
Get the issue's GraphQL node ID:
ISSUE_ID=$(gh api graphql -f query='
query { repository(owner: "penpot", name: "penpot") {
issue(number: <ISSUE_NUMBER>) { id }
}}' --jq '.data.repository.issue.id')
Issue Type IDs for the Penpot repo:
| Type | ID |
|---|---|
| Bug | IT_kwDOAcyBPM4AX5Nb |
| Enhancement | IT_kwDOAcyBPM4B_IQN |
| Feature | IT_kwDOAcyBPM4AX5Nf |
| Task | IT_kwDOAcyBPM4AX5NY |
| Question | IT_kwDOAcyBPM4B_IQj |
| Docs | IT_kwDOAcyBPM4B_IQz |
Set it:
gh api graphql -f query='
mutation {
updateIssue(input: {
id: "'"$ISSUE_ID"'"
issueTypeId: "<TYPE_ID>"
}) {
issue { number issueType { name } }
}
}'
gh issue view <ISSUE_NUMBER> --repo penpot/penpot \
--json title,milestone,projectItems,labels \
--jq '{title, milestone: .milestone.title, projects: [.projectItems[].title], labels: [.labels[].name]}'
gh api graphql -f query='
query { repository(owner: "penpot", name: "penpot") {
issue(number: <ISSUE_NUMBER>) { issueType { name } }
}}' --jq '.data.repository.issue.issueType.name'
Append Closes #<ISSUE_NUMBER> to the PR body:
gh pr view <PR_NUMBER> --repo penpot/penpot --json body --jq '.body' > /tmp/pr-body.md
printf "\n\nCloses #<ISSUE_NUMBER>\n" >> /tmp/pr-body.md
gh pr edit <PR_NUMBER> --repo penpot/penpot --body-file /tmp/pr-body.md
# Verify
gh pr view <PR_NUMBER> --repo penpot/penpot --json body \
--jq '.body | test("Closes #<ISSUE_NUMBER>")'
Note: If the PR is already merged, Closes won't auto-close the issue
ā it only creates the "Development" sidebar link. This is the desired
behavior since the issue is a tracking artifact.
rm -f /tmp/issue-body.md /tmp/pr-body.md
| PR has | Issue gets |
|---|---|
bug | bug |
enhancement | enhancement |
community contribution | community contribution |
backport candidate | (skip ā workflow label) |
team-qa | (skip ā workflow label) |
| No user-facing label | Infer from title: :bug: ā bug, :sparkles: ā enhancement |
| PR label(s) / title prefix | Issue Type |
|---|---|
bug or :bug: | Bug |
enhancement or :sparkles: or :tada: | Enhancement |
| Feature / epic | Feature |
| Documentation | Docs |
| None of the above | Task |
gh issue create can't set it.Closes #<NUMBER> creates the "Development"
sidebar link automatically.community contribution
label or the author is not a core team member, add the label to the issue.Update the project CHANGES.md with issues from a given GitHub milestone, with correct categorization and references.
Fetch information from Taiga public API for the Penpot project (id 345963) ā issues, user stories, and tasks, without authentication.
Evaluate Clojure code via nREPL using the standalone tools/nrepl-eval.mjs CLI tool.
Port changes from a specific Git commit to the current branch by manually applying the diff, avoiding cherry-pick when it would introduce complex conflicts.