Skip to content

docs: add Labels section to CONTRIBUTING.md - #200

Closed
Reggiebro wants to merge 1 commit into
DepRadarOrg:mainfrom
Reggiebro:docs/labels-guide
Closed

Reggiebro wants to merge 1 commit into
DepRadarOrg:mainfrom
Reggiebro:docs/labels-guide

Conversation

@Reggiebro

Copy link
Copy Markdown

What

Adds a Labels section to CONTRIBUTING.md documenting every label on the repo and when it's used, split into two tables:

  • Area labels — typosquat, scanner, crawler, cve, contract, client, frontend, wallet, cli, npm, pypi, crates, drips, data, security, performance, accessibility, behavioral, testing, ci, devex, tooling, design
  • Workflow labels — bug, enhancement, documentation, question, good first issue, help wanted, duplicate, invalid, wontfix, Stellar Wave

Guidance covers one-area-label-per-issue, and notes that Stellar Wave is maintainer-applied for Drips funding eligibility (don't self-assign, but you can filter by it to find payable work).

Acceptance criteria

  • All commands and links in the new docs verified — label names/descriptions taken from the live repo label set; the Drips link resolves
  • PROGRESS.md entry added

Closes #185

Documents every area label (typosquat, scanner, contract, frontend, ...)
and workflow label (bug, good first issue, Stellar Wave, ...) in two
tables, with guidance on when each is used. Notes that Stellar Wave is
maintainer-applied for Drips funding eligibility and should not be
self-assigned.

Adds the required PROGRESS.md entry.

Closes DepRadarOrg#185
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[docs] Issue and PR labels guide

2 participants