Files
skills/public/collaboration-github-issues-projects.html
zeekayandHanzo Dev 9e10c1c10e Each llms index points at the other two
hanzoskills.com/llms.txt now opens with the install line, the API
reference index and the company index, so an agent that lands on any
one of the three can find the rest.

robots.txt claimed 537 documents while llms.txt counts 920. The number
is gone from robots.txt; llms.txt derives it.

public/ is regenerated from scripts/site.py, which it had fallen
behind: the copy-prompt menu and agent bar were in the generator and
not in the committed pages. tests/site.mjs passes against the result.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-11 00:27:59 -07:00

699 lines
30 KiB
HTML

<!doctype html>
<html lang="en"><head>
<meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1">
<title>collaboration-github-issues-projects</title>
<meta name="color-scheme" content="dark">
<style>
/* Committed to one visual world: a dark instrument panel. No light variant —
the dot field and the hairline rules only read on black, and a naive
inversion would wash both out. Every colour is painted explicitly so the page
never borrows a host background. */
@font-face{font-family:'Zen';src:url('/fonts/Zen-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
@font-face{font-family:'Zen';src:url('/fonts/Zen-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
@font-face{font-family:'Zen Pixel Square';src:url('/fonts/ZenPixel-Square.woff2') format('woff2');font-style:normal;font-display:swap}
:root{
--ink:#f4f4f2; --soft:#9c9c98; --faint:#6a6a66; --ground:#000; --panel:#0a0a0a;
--line:#232323; --line-hi:#3a3a3a; --accent:#f4f4f2;
--font-zen-sans:'Zen',-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif;
--font-zen-mono:'Zen Mono',ui-monospace,"SF Mono",SFMono-Regular,Menlo,Consolas,monospace;
--font-zen-pixel-square:'Zen Pixel Square',monospace;
--mono:var(--font-zen-mono);
--sans:var(--font-zen-sans);
/* Controls are pills and surfaces are soft, as on hanzo.ai. */
--r:999px; --r-soft:14px;
}
*{box-sizing:border-box}
html{-webkit-text-size-adjust:100%}
body{margin:0;background:var(--ground);color:var(--ink);font-family:var(--sans);
font-size:16px;line-height:1.65;-webkit-font-smoothing:antialiased}
.wrap{max-width:60rem;margin:0 auto;padding:0 1.75rem}
/* The dot field. A halftone made of one repeating radial-gradient, faded out
along the diagonal by a mask so it reads as a wave rather than wallpaper. */
/* No overflow clip here: the dot field is inset to the box already, and a clip
would cut off the copy-prompt menu. */
.hero{position:relative;border-bottom:1px solid var(--line)}
.hero::before{content:"";position:absolute;inset:0;
background-image:radial-gradient(var(--line-hi) 1px, transparent 1px);
background-size:7px 7px;
-webkit-mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
pointer-events:none}
.hero .wrap{position:relative;padding-top:5.5rem;padding-bottom:4rem}
nav{border-bottom:1px solid var(--line)}
nav .in{max-width:60rem;margin:0 auto;padding:1.1rem 1.75rem;display:flex;
justify-content:space-between;align-items:center;gap:1rem}
.brand{font-family:var(--mono);font-size:.85rem;letter-spacing:.14em;
text-transform:uppercase;color:var(--ink);text-decoration:none;
display:inline-flex;align-items:center;gap:.6rem}
.brand i{font-style:normal;color:var(--faint)}
.mark{width:1.15em;height:1.15em;display:block;flex:0 0 auto}
nav a.up{font-family:var(--mono);font-size:.72rem;letter-spacing:.14em;
text-transform:uppercase;color:var(--soft);text-decoration:none}
nav a.up:hover{color:var(--ink)}
h1{font-family:var(--mono);font-size:clamp(2rem,5.4vw,3.4rem);line-height:1.12;
letter-spacing:-.02em;margin:0 0 1.1rem;font-weight:500;text-wrap:balance}
h1 em{font-style:normal;color:var(--faint)}
.lede{color:var(--soft);font-size:1.05rem;max-width:52ch;margin:0 0 2.25rem}
.btns{display:flex;flex-wrap:wrap;gap:.7rem;margin:0 0 .5rem;align-items:center}
.btn{display:inline-flex;align-items:center;gap:.5rem;font-family:var(--mono);
font-size:.72rem;letter-spacing:.14em;text-transform:uppercase;
padding:.8rem 1.4rem;border:1px solid var(--line-hi);border-radius:var(--r);
color:var(--ink);text-decoration:none;background:transparent;cursor:pointer;
line-height:1.2;font-weight:400}
.btn:hover{background:#141414;text-decoration:none;border-color:var(--soft)}
.btn.solid{background:var(--ink);color:#000;border-color:var(--ink)}
.btn.solid:hover{background:#d8d8d4}
.btn .chev{width:.7em;height:.7em;flex:0 0 auto;transition:transform .15s ease}
.btn[aria-expanded="true"] .chev{transform:rotate(180deg)}
/* Copy-prompt selector. Each row copies the prompt for its own target. */
.copy{position:relative;display:inline-flex}
.menu{position:absolute;top:calc(100% + .5rem);left:0;z-index:20;min-width:21rem;
background:var(--panel);border:1px solid var(--line-hi);border-radius:var(--r-soft);
padding:.4rem;display:flex;flex-direction:column;
box-shadow:0 12px 32px rgba(0,0,0,.75)}
.menu[hidden]{display:none}
.mi{display:flex;align-items:center;gap:.7rem;width:100%;text-align:left;
padding:.62rem .8rem;border:0;border-radius:calc(var(--r-soft) - .35rem);
background:transparent;color:var(--ink);font-family:var(--mono);font-size:.76rem;
letter-spacing:.04em;text-decoration:none;cursor:pointer;line-height:1.3;
white-space:nowrap}
.mi:hover,.mi:focus-visible{background:#181818;outline:none}
.mi .mark{width:1.05rem;height:1.05rem;color:var(--soft)}
.mi:hover .mark{color:var(--ink)}
.mi u{margin-left:auto;color:var(--faint);text-decoration:none;font-size:.68rem;
letter-spacing:.1em;text-transform:uppercase}
/* Works-with bar: one scrolling row, name and mark per agent. */
.strip{border-bottom:1px solid var(--line);background:var(--panel)}
.strip .in{max-width:60rem;margin:0 auto;padding:.9rem 1.75rem;display:flex;
align-items:center;gap:1.25rem;font-family:var(--mono);font-size:.72rem;
letter-spacing:.1em;text-transform:uppercase;color:var(--faint)}
.strip b{color:var(--soft);font-weight:400;flex:0 0 auto;
border-right:1px solid var(--line);padding-right:1.25rem;align-self:stretch;
display:flex;align-items:center}
.bar{display:flex;align-items:center;gap:.5rem;flex:1 1 auto;min-width:0;
overflow-x:auto;scrollbar-width:none;scroll-snap-type:x proximity;
-webkit-overflow-scrolling:touch;
-webkit-mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent);
mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent)}
.bar::-webkit-scrollbar{display:none}
.agent{display:inline-flex;align-items:center;gap:.45rem;flex:0 0 auto;
padding:.4rem .85rem;border:1px solid var(--line);border-radius:var(--r);
color:var(--soft);white-space:nowrap;scroll-snap-align:start;
text-decoration:none;background:var(--ground)}
.agent:hover{color:var(--ink);border-color:var(--line-hi);text-decoration:none}
.agent .mark{width:.95rem;height:.95rem}
h2{font-family:var(--mono);font-size:1.1rem;letter-spacing:-.01em;margin:2.75rem 0 .75rem;font-weight:500}
h3{font-size:1rem;margin:2rem 0 .5rem;font-weight:600}
h4,h5,h6{font-size:.94rem;margin:1.5rem 0 .5rem;font-weight:600}
p{margin:0 0 1rem;max-width:70ch}
ul,ol{margin:0 0 1rem;padding-left:1.35rem;max-width:70ch}
li{margin:.22rem 0}
a{color:var(--ink);text-decoration:underline;text-underline-offset:3px;
text-decoration-color:var(--line-hi)}
a:hover{text-decoration-color:var(--ink)}
a:focus-visible{outline:1px solid var(--ink);outline-offset:3px}
code{font-family:var(--mono);font-size:.85em;background:var(--panel);
border:1px solid var(--line);border-radius:5px;padding:.1em .36em}
pre{background:var(--panel);border:1px solid var(--line);padding:1rem 1.1rem;
border-radius:var(--r-soft);overflow-x:auto;margin:0 0 1.25rem}
pre code{background:none;border:0;padding:0;font-size:.82rem;line-height:1.7}
blockquote{margin:0 0 1rem;padding-left:1rem;border-left:1px solid var(--line-hi);color:var(--soft)}
hr{border:0;border-top:1px solid var(--line);margin:2.5rem 0}
table{border-collapse:collapse;width:100%;margin:0 0 1.25rem;font-size:.92rem;
display:block;overflow-x:auto}
th,td{border:1px solid var(--line);padding:.5rem .7rem;text-align:left}
.curl{display:block;background:var(--panel);border:1px solid var(--line);
border-radius:var(--r-soft);padding:.95rem 1.1rem;font-family:var(--mono);
font-size:.8rem;color:var(--soft);overflow-x:auto;margin:0 0 2.5rem;
white-space:pre;line-height:1.9}
.curl b{color:var(--ink);font-weight:400}
.curl i{font-style:normal;color:var(--faint)}
/* index */
#q{width:100%;padding:.85rem 1.2rem;font-family:var(--mono);font-size:.85rem;color:var(--ink);
background:var(--panel);border:1px solid var(--line);border-radius:var(--r);margin:0 0 .6rem}
#q::placeholder{color:var(--faint);text-transform:uppercase;letter-spacing:.1em;font-size:.72rem}
#q:focus{outline:none;border-color:var(--soft)}
#count{color:var(--faint);font-family:var(--mono);font-size:.72rem;letter-spacing:.1em;
text-transform:uppercase;margin:0 0 2rem}
.cat{margin:2.5rem 0 .5rem;font-family:var(--mono);font-size:.7rem;letter-spacing:.16em;
text-transform:uppercase;color:var(--faint);border-bottom:1px solid var(--line);
padding-bottom:.45rem}
.row{display:block;padding:.6rem .9rem;margin:0 -.9rem;border-bottom:1px solid var(--line);
border-radius:var(--r-soft);text-decoration:none}
.row:hover{background:#0a0a0a}
.nm{font-family:var(--mono);font-size:.84rem;color:var(--ink);display:block}
.ds{color:var(--soft);font-size:.9rem;display:block;margin-top:.12rem}
footer{margin-top:4rem;padding:2rem 0 4rem;border-top:1px solid var(--line);
color:var(--faint);font-size:.85rem}
footer a{color:var(--soft)}
.fmap{display:grid;gap:1.75rem;grid-template-columns:repeat(auto-fit,minmax(11rem,1fr));
margin:0 0 2rem;font-size:.85rem}
.fmap b{display:block;font-family:var(--mono);font-size:.68rem;letter-spacing:.16em;
text-transform:uppercase;color:var(--faint);font-weight:400;margin:0 0 .6rem;
border-bottom:1px solid var(--line);padding-bottom:.4rem}
.fmap a{display:inline-block;color:var(--ink);text-decoration:none;margin:.3rem .35rem 0 0}
.fmap a:hover{text-decoration:underline}
.fmap div{color:var(--faint);line-height:1.5}
.fend{border-top:1px solid var(--line);padding-top:1.25rem;font-size:.82rem}
@media (max-width:640px){
.hero .wrap{padding-top:3.25rem;padding-bottom:2.75rem}
.btns{gap:.5rem}
.btn{padding:.75rem 1.15rem;font-size:.68rem}
.copy,.copy .btn{width:100%;justify-content:center}
.menu{left:0;right:0;min-width:0}
.strip .in{flex-direction:column;align-items:flex-start;gap:.6rem;padding:.9rem 1.75rem}
.strip b{border-right:0;padding-right:0}
.bar{width:100%}
}
</style>
<link rel="alternate" type="text/markdown" href="/collaboration-github-issues-projects.md">
<link rel="icon" href="/favicon.svg">
<link rel="canonical" href="https://hanzoskills.com/collaboration-github-issues-projects">
</head>
<!-- Reading this with a machine? Every page here is also plain markdown.
This one: https://hanzoskills.com/collaboration-github-issues-projects.md
Index: https://hanzoskills.com/llms.txt
Corpus: https://hanzoskills.com/all.md
Append .md to any path for the markdown twin. -->
<body>
<nav><div class="in">
<a class="brand" href="/"><svg class="mark" viewBox="0 0 67 67" fill="currentColor" aria-hidden="true"><path d="M22.21 67V44.6369H0V67H22.21Z"/><path d="M66.7038 22.3184H22.2534L0.0878906 44.6367H44.4634L66.7038 22.3184Z"/><path d="M22.21 0H0V22.3184H22.21V0Z"/><path d="M66.7198 0H44.5098V22.3184H66.7198V0Z"/><path d="M66.7198 67V44.6369H44.5098V67H66.7198Z"/></svg> HANZO<i>SKILLS</i></a>
<a class="up" href="/">All skills</a>
</div></nav>
<div class="wrap">
<h1>collaboration-github-issues-projects</h1><p class="lede">Issue management, templates, labels, milestones, GitHub Projects, and issue linking workflows</p><h1>GitHub Issues and Projects</h1>
<p><strong>Scope</strong>: Issue creation and templates, labels and organization, milestones, GitHub Projects (beta), issue linking, Discussions vs Issues, and project automation</p>
<p><strong>Lines</strong>: ~290</p>
<p><strong>Last Updated</strong>: 2025-10-25</p>
<p><strong>Format Version</strong>: 1.0 (Atomic)</p>
<hr>
<h2>When to Use This Skill</h2>
<p>Activate this skill when:</p>
<ul><li>Creating and managing GitHub issues</li><li>Setting up issue templates for consistent reporting</li><li>Organizing issues with labels and milestones</li><li>Using GitHub Projects for project management</li><li>Linking issues to pull requests and commits</li><li>Choosing between Discussions and Issues</li><li>Automating issue triage and project workflows</li><li>Planning releases with milestones</li><li>Tracking work with project boards</li></ul>
<hr>
<h2>Core Concepts</h2>
<h3>Issue Lifecycle</h3>
<pre><code>Created → Triaged → Assigned → In Progress → PR Linked → Closed
↓ ↓ ↓ ↓ ↓ ↓
Labels Priority Owner Development Review Resolved</code></pre>
<p><strong>States</strong>:</p>
<ul><li><strong>Open</strong>: Active issue requiring attention</li><li><strong>Closed</strong>: Resolved, won&#x27;t fix, or duplicate</li><li><strong>Locked</strong>: Prevents further comments</li><li><strong>Pinned</strong>: Highlighted at top of issues list</li></ul>
<h3>Label System</h3>
<p><strong>Categories</strong>:</p>
<ul><li><strong>Type</strong>: bug, enhancement, documentation, question</li><li><strong>Priority</strong>: critical, high, medium, low</li><li><strong>Status</strong>: needs-triage, in-progress, blocked, ready</li><li><strong>Area</strong>: frontend, backend, api, infrastructure</li><li><strong>Effort</strong>: good-first-issue, help-wanted, complex</li></ul>
<h3>GitHub Projects Structure</h3>
<p><strong>New Projects (beta)</strong>:</p>
<ul><li>Table view, board view, roadmap view</li><li>Custom fields (status, priority, size, iteration)</li><li>Automation rules</li><li>Filtering and grouping</li><li>Cross-repository support</li></ul>
<hr>
<h2>Patterns</h2>
<h3>Creating Issues with GitHub CLI</h3>
<pre><code class="lang-bash"># Create basic issue
gh issue create
# Create with title and body
gh issue create \
--title &quot;Fix login timeout bug&quot; \
--body &quot;Users are getting timeout errors after 30 seconds&quot;
# Create with labels and assignees
gh issue create \
--title &quot;Add dark mode support&quot; \
--label enhancement,frontend \
--assignee @me
# Create from template
gh issue create --template bug_report.md
# Create with milestone
gh issue create \
--title &quot;Optimize database queries&quot; \
--milestone &quot;v2.0.0&quot;
# Create from file
gh issue create --title &quot;Bug report&quot; --body-file issue.md
# List issues
gh issue list
# List with filters
gh issue list --label bug --state open
gh issue list --assignee @me
gh issue list --milestone &quot;v1.0.0&quot;
# View issue
gh issue view 123
# Close issue
gh issue close 123 --comment &quot;Fixed in PR #456&quot;
# Reopen issue
gh issue reopen 123</code></pre>
<h3>Issue Templates</h3>
<p><strong>Bug report template</strong> (.github/ISSUE_TEMPLATE/bug_report.yml):</p>
<pre><code class="lang-yaml">name: Bug Report
description: File a bug report
title: &quot;[Bug]: &quot;
labels: [&quot;bug&quot;, &quot;needs-triage&quot;]
assignees:
- octocat
body:
- type: markdown
attributes:
value: |
Thanks for taking the time to fill out this bug report!
- type: input
id: contact
attributes:
label: Contact Details
description: How can we get in touch with you if we need more info?
placeholder: ex. [email protected]
validations:
required: false
- type: textarea
id: what-happened
attributes:
label: What happened?
description: Also tell us, what did you expect to happen?
placeholder: Tell us what you see!
value: &quot;A bug happened!&quot;
validations:
required: true
- type: dropdown
id: version
attributes:
label: Version
description: What version of our software are you running?
options:
- 1.0.2 (Default)
- 1.0.3 (Edge)
default: 0
validations:
required: true
- type: dropdown
id: browsers
attributes:
label: What browsers are you seeing the problem on?
multiple: true
options:
- Firefox
- Chrome
- Safari
- Microsoft Edge
- type: textarea
id: logs
attributes:
label: Relevant log output
description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
render: shell
- type: checkboxes
id: terms
attributes:
label: Code of Conduct
description: By submitting this issue, you agree to follow our [Code of Conduct](https://example.com)
options:
- label: I agree to follow this project&#x27;s Code of Conduct
required: true</code></pre>
<p><strong>Feature request template</strong> (.github/ISSUE_TEMPLATE/feature_request.md):</p>
<pre><code class="lang-markdown">---
name: Feature Request
about: Suggest an idea for this project
title: &#x27;[FEATURE] &#x27;
labels: enhancement
assignees: &#x27;&#x27;
---
## Problem Statement
A clear description of the problem this feature would solve.
Ex. I&#x27;m always frustrated when [...]
## Proposed Solution
A clear description of what you want to happen.
## Alternatives Considered
Any alternative solutions or features you&#x27;ve considered.
## Additional Context
Add any other context, screenshots, or examples about the feature request here.
## Implementation Notes (Optional)
If you have ideas about how to implement this, share them here.</code></pre>
<p><strong>Template chooser</strong> (.github/ISSUE_TEMPLATE/config.yml):</p>
<pre><code class="lang-yaml">blank_issues_enabled: false
contact_links:
- name: Community Support
url: https://github.com/org/repo/discussions
about: Please ask questions and discuss ideas here
- name: Security Issue
url: https://github.com/org/repo/security/advisories/new
about: Report security vulnerabilities privately</code></pre>
<h3>Label Management</h3>
<pre><code class="lang-bash"># Create label
gh label create &quot;priority:high&quot; \
--description &quot;High priority issue&quot; \
--color &quot;d73a4a&quot;
# List labels
gh label list
# Edit label
gh label edit &quot;bug&quot; --color &quot;ff0000&quot;
# Delete label
gh label delete &quot;old-label&quot;
# Add labels to issue
gh issue edit 123 --add-label &quot;bug,priority:high&quot;
# Remove labels
gh issue edit 123 --remove-label &quot;needs-triage&quot;</code></pre>
<p><strong>Standard label set</strong>:</p>
<pre><code>Type:
bug (d73a4a - red)
enhancement (a2eeef - blue)
documentation (0075ca - dark blue)
question (d876e3 - purple)
Priority:
priority:critical (b60205 - dark red)
priority:high (d93f0b - orange)
priority:medium (fbca04 - yellow)
priority:low (0e8a16 - green)
Status:
needs-triage (ffffff - white)
in-progress (1d76db - blue)
blocked (e99695 - light red)
ready-for-review (c2e0c6 - light green)
Effort:
good-first-issue (7057ff - purple)
help-wanted (008672 - teal)
complex (c5def5 - light blue)</code></pre>
<h3>Milestones</h3>
<pre><code class="lang-bash"># Create milestone
gh api repos/owner/repo/milestones \
--method POST \
--field title=&quot;v2.0.0&quot; \
--field description=&quot;Major release with new features&quot; \
--field due_on=&quot;2025-12-31T23:59:59Z&quot;
# List milestones
gh api repos/owner/repo/milestones
# Assign issue to milestone
gh issue edit 123 --milestone &quot;v2.0.0&quot;
# View milestone progress
gh api repos/owner/repo/milestones | \
jq &#x27;.[] | {title, open_issues, closed_issues}&#x27;</code></pre>
<p><strong>Milestone planning</strong>:</p>
<pre><code>v1.0.0 (MVP)
├── Authentication system
├── Core API endpoints
├── Basic UI components
└── Initial documentation
v1.1.0 (Enhancements)
├── Advanced search
├── Export functionality
├── Performance improvements
└── Expanded docs
v2.0.0 (Major Release)
├── New architecture
├── Breaking API changes
├── Modern UI redesign
└── Migration guide</code></pre>
<h3>GitHub Projects (New Beta)</h3>
<p><strong>Creating a project</strong> (via Web UI):</p>
<ol><li>Click &quot;Projects&quot; → &quot;New project&quot;</li><li>Choose template: Board, Table, Roadmap</li><li>Add custom fields:</li></ol>
<ul><li>Status (Todo, In Progress, Done)</li><li>Priority (Low, Medium, High, Critical)</li><li>Size (S, M, L, XL)</li><li>Iteration (Sprint 1, Sprint 2, etc.)</li></ul>
<p><strong>Adding items</strong>:</p>
<pre><code class="lang-bash"># Add issue to project (requires project ID)
gh project item-add &lt;project-id&gt; --owner @me --url https://github.com/owner/repo/issues/123
# Or via web UI:
# 1. Open project
# 2. Click &quot;Add item&quot;
# 3. Search for issues/PRs</code></pre>
<p><strong>Automation example</strong>:</p>
<pre><code class="lang-yaml"># Auto-add issues to project
# Settings → Actions → New workflow
name: Add to project
on:
issues:
types: [opened]
jobs:
add-to-project:
runs-on: ubuntu-latest
steps:
- uses: actions/[email protected]
with:
project-url: https://github.com/orgs/org/projects/1
github-token: ${{ secrets.ADD_TO_PROJECT_PAT }}</code></pre>
<p><strong>Project views</strong>:</p>
<ul><li><strong>Table</strong>: Spreadsheet-like view with custom fields</li><li><strong>Board</strong>: Kanban board grouped by status</li><li><strong>Roadmap</strong>: Timeline view with date fields</li></ul>
<h3>Issue Linking</h3>
<p><strong>Link issues to PRs</strong>:</p>
<pre><code class="lang-bash"># In PR description or commit message
Closes #123
Fixes #456
Resolves #789
# Multiple issues
Closes #123, #456, #789
# Cross-repository
Fixes owner/other-repo#123</code></pre>
<p><strong>Keywords that auto-close issues</strong>:</p>
<ul><li><code>close</code>, <code>closes</code>, <code>closed</code></li><li><code>fix</code>, <code>fixes</code>, <code>fixed</code></li><li><code>resolve</code>, <code>resolves</code>, <code>resolved</code></li></ul>
<p><strong>Example PR description</strong>:</p>
<pre><code class="lang-markdown">## Summary
Adds rate limiting to API endpoints.
## Changes
- Implements Redis-based rate limiter
- Adds configuration for limits per endpoint
- Includes tests
Closes #456
Related to #123, #234</code></pre>
<p><strong>Link issues to commits</strong>:</p>
<pre><code class="lang-bash">git commit -m &quot;Add rate limiting
Implements Redis-based rate limiter to prevent API abuse.
Fixes #456&quot;</code></pre>
<h3>Discussions vs Issues</h3>
<p><strong>Use Discussions for</strong>:</p>
<ul><li>Questions and answers</li><li>Ideas and brainstorming</li><li>Announcements</li><li>Community conversation</li><li>Open-ended topics</li></ul>
<p><strong>Use Issues for</strong>:</p>
<ul><li>Bug reports</li><li>Specific feature requests</li><li>Actionable tasks</li><li>Trackable work items</li><li>Release planning</li></ul>
<pre><code class="lang-bash"># Create discussion (via Web UI)
# Discussions tab → New discussion
# Choose category: Announcements, General, Ideas, Q&amp;A, Show and tell
# Convert issue to discussion
gh issue close 123 --comment &quot;Moving to Discussions&quot;
# Then manually create discussion</code></pre>
<hr>
<h2>Quick Reference</h2>
<h3>GitHub CLI Issue Commands</h3>
<pre><code class="lang-bash"># Create and manage
gh issue create [flags] # Create issue
gh issue list [flags] # List issues
gh issue view &lt;number&gt; # View issue details
gh issue edit &lt;number&gt; [flags] # Edit issue
# Workflow
gh issue close &lt;number&gt; # Close issue
gh issue reopen &lt;number&gt; # Reopen issue
gh issue pin &lt;number&gt; # Pin issue
gh issue unpin &lt;number&gt; # Unpin issue
# Labels and milestones
gh label create &lt;name&gt; [flags] # Create label
gh label list # List labels</code></pre>
<h3>Issue Linking Keywords</h3>
<pre><code>Auto-close keywords:
close, closes, closed
fix, fixes, fixed
resolve, resolves, resolved
Usage in PRs or commits:
Closes #123
Fixes #456
Resolves owner/repo#789
Reference only (no auto-close):
Related to #123
See also #456
Part of #789</code></pre>
<h3>Project Management Best Practices</h3>
<pre><code>✅ DO: Use templates for consistent issue reporting
✅ DO: Triage new issues within 24-48 hours
✅ DO: Apply labels for categorization and filtering
✅ DO: Use milestones for release planning
✅ DO: Link PRs to issues for traceability
✅ DO: Close stale issues with explanation
✅ DO: Pin important issues for visibility
❌ DON&#x27;T: Leave issues unlabeled
❌ DON&#x27;T: Create duplicate issues without checking
❌ DON&#x27;T: Use issues for questions (use Discussions)
❌ DON&#x27;T: Close issues without resolution or explanation
❌ DON&#x27;T: Ignore issue templates</code></pre>
<hr>
<h2>Anti-Patterns</h2>
<h3>❌ No Issue Templates</h3>
<pre><code class="lang-markdown"># WRONG: Users create inconsistent issues
Title: it doesn&#x27;t work
Body: when I click the button nothing happens</code></pre>
<p><strong>Problems</strong>:</p>
<ul><li>Missing critical information</li><li>Time wasted asking for details</li><li>Difficult to reproduce bugs</li><li>Inconsistent issue quality</li></ul>
<pre><code class="lang-markdown"># CORRECT: Use structured templates
Title: [Bug] Login button unresponsive on mobile Safari
**Environment:**
- OS: iOS 17.0
- Browser: Safari 17.0
- App Version: 1.2.3
**Steps to Reproduce:**
1. Open app on iPhone
2. Navigate to login page
3. Tap &quot;Login&quot; button
4. Nothing happens
**Expected:** Login modal appears
**Actual:** No response to tap
**Console Errors:**
TypeError: Cannot read property &#x27;addEventListener&#x27; of null</code></pre>
<h3>❌ Poor Label Organization</h3>
<pre><code class="lang-bash"># WRONG: Random, inconsistent labels
bug1, bug2, needs work, todo, urgent, ASAP, help</code></pre>
<p><strong>Problems</strong>:</p>
<ul><li>Can&#x27;t filter effectively</li><li>No consistent categorization</li><li>Unclear priorities</li><li>Difficult to track progress</li></ul>
<pre><code class="lang-bash"># CORRECT: Structured label system
Type: bug, enhancement, documentation
Priority: priority:critical, priority:high, priority:medium, priority:low
Status: needs-triage, in-progress, blocked
Area: frontend, backend, api, infrastructure
Effort: good-first-issue, help-wanted</code></pre>
<h3>❌ Issues Not Linked to PRs</h3>
<pre><code class="lang-bash"># WRONG: PR merged without closing issue
# Issue #123 remains open
# No connection between fix and issue</code></pre>
<p><strong>Problems</strong>:</p>
<ul><li>Issues stay open after fix</li><li>No audit trail</li><li>Difficult to find related code changes</li><li>Duplicated work</li></ul>
<pre><code class="lang-bash"># CORRECT: Link PRs to issues
# In PR description:
Fixes #123
# Or in commit message:
git commit -m &quot;Add rate limiting
Implements Redis-based rate limiter.
Closes #123&quot;
# Result: Issue automatically closed when PR merges</code></pre>
<h3>❌ Ignoring Stale Issues</h3>
<pre><code class="lang-bash"># WRONG: 500 open issues, many years old
# No activity on 300+ issues
# Overwhelms actual work</code></pre>
<p><strong>Problems</strong>:</p>
<ul><li>Can&#x27;t see what&#x27;s actually active</li><li>Outdated issues confuse contributors</li><li>No clear priorities</li><li>Looks unmaintained</li></ul>
<pre><code class="lang-bash"># CORRECT: Manage stale issues
# 1. Use Stale bot or GitHub Actions
# 2. Close inactive issues after 60-90 days
# 3. Add &quot;stale&quot; label after 30 days warning
# 4. Allow &quot;keep-alive&quot; label to prevent closure
# Example workflow:
# .github/workflows/stale.yml
name: Close stale issues
on:
schedule:
- cron: &#x27;0 0 * * *&#x27; # Daily
jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v8
with:
stale-issue-message: &#x27;This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.&#x27;
close-issue-message: &#x27;Closing due to inactivity.&#x27;
days-before-stale: 60
days-before-close: 7
exempt-issue-labels: &#x27;keep-alive,roadmap&#x27;</code></pre>
<h3>❌ Using Issues for Discussions</h3>
<pre><code class="lang-bash"># WRONG: Creating issues for questions
Title: How do I configure the API?
Body: I don&#x27;t understand the documentation...</code></pre>
<p><strong>Problems</strong>:</p>
<ul><li>Clutters issue tracker</li><li>Not actionable work items</li><li>Difficult to search for bugs</li><li>Wastes project management overhead</li></ul>
<pre><code class="lang-bash"># CORRECT: Use Discussions for questions
# Enable Discussions in repository
# Settings → Features → Discussions
# Create categories:
# - Q&amp;A: Questions and answers
# - Ideas: Feature brainstorming
# - General: Community chat
# - Announcements: Project updates
# Use Issues only for:
# - Bug reports
# - Specific feature requests
# - Actionable tasks</code></pre>
<hr>
<h2>Related Skills</h2>
<ul><li><code>collaboration/github/github-pull-requests.md</code> - Linking PRs to issues</li><li><code>collaboration/github/github-repository-management.md</code> - Issue and PR templates setup</li><li><code>collaboration/github/github-actions-workflows.md</code> - Automating issue workflows</li><li><code>project-management/agile-workflows.md</code> - Sprint planning with milestones</li><li><code>documentation/technical-writing.md</code> - Writing clear issue descriptions</li></ul>
<hr>
<p><strong>Last Updated</strong>: 2025-10-25</p>
<p><strong>Format Version</strong>: 1.0 (Atomic)</p>
<footer>
<div class="fmap">
<div><b>Build</b>
<a href="https://hanzo.app">hanzo.app</a> app builder
<a href="https://hanzo.codes">hanzo.codes</a> code with an agent
<a href="https://hanzoskills.com">hanzoskills.com</a> what an agent reads</div>
<div><b>Run</b>
<a href="https://console.hanzo.ai">console.hanzo.ai</a> cloud console
<a href="https://api.hanzo.ai">api.hanzo.ai</a> the API</div>
<div><b>Account</b>
<a href="https://hanzo.id">hanzo.id</a> sign in
<a href="https://pay.hanzo.ai">pay.hanzo.ai</a> top up
<a href="https://billing.hanzo.ai">billing.hanzo.ai</a> invoices and usage</div>
<div><b>Company</b>
<a href="https://hanzo.ai">hanzo.ai</a> canonical
<a href="https://hanzo.ventures">hanzo.ventures</a> ventures</div>
</div>
<div class="fend"><a href="/collaboration-github-issues-projects.md">This page as plain text</a> · <a href="/llms.txt">Index for agents</a></div>
</footer>
</div></body></html>