You already picked a ticket. This page is the claim: one comment, maybe the Assignees field, then you work.

It is not how to choose the ticket. That is how to pick an issue that will get merged. It is not fork, clone, and open the PR. That is the first pull request guide. After someone reviews the diff, how to respond to code review. If the PR sits silent, what to do when your PR is ignored.

A claim is a reservation, not a conversation. One short intent comment. Then code.

One comment, then work

Leave one comment on one issue.

Say you are taking it. Say you will open a PR. If CONTRIBUTING asked for a timeline, give a real one (this weekend, not “soon”). Then stop typing.

Do not ask “is anyone working on this?” Do not ask it again tomorrow. Do not @-mention every maintainer. Do not open a second comment to “just check in” before you have a branch.

Wait a beat if the project said to wait for assignment. If they did not, the comment is the claim. Start.

Template: short intent, not an essay

Paste something this short:

I’ll take this. Planning a PR that does X (the change the issue already named). Aiming to open it by DATE.

That is the whole template. No resume. No “first contribution, please be nice.” No dump of your approach essay. No screenshots of your local clone.

If the spec is fuzzy, one clarifying question in that same comment. Then wait for the answer. Two questions means you picked a wishlist — go back to picking.

Assignees only if the project allows it

Some repos let you self-assign. Some have a bot. Some forbid it.

Read CONTRIBUTING.md and the issue template. If they say “comment, do not assign yourself,” do not assign yourself. If they use a /assign bot, use that once. If the Assignees dropdown is disabled, that is the answer.

A self-assign on a repo that forbids it looks like you skipped the guide. The comment still works. The extra click does not make you first.

Do not assign other people. Do not unassign someone else so you can take the slot.

If someone already claimed: leave it

Read the thread before you type.

A recent “I’ll take this,” an assignee, a linked draft PR — leave it. Piling on is how you become the third person asking the same question.

A claim from months ago with no PR and no update is stalled. That is a pick problem, not a claim problem. Do not stack a second “still interested?” on a dead reservation. Use how to pick an issue that will get merged and find a thread nobody reserved. Maintainers sometimes clear stale claims. You are not the janitor.

If the issue is a waiting room of eight “assign me” comments, walk out. You are not first.

Do not pile on stale claims

Stale is not a license to spam.

Do not comment “still available?” on every old good first issue.
Do not claim five issues “in case one is taken.”
Do not keep a claim you will not finish. One line: you are dropping it. Then leave.

A leftover claim you abandoned is how the next person wastes a weekend. Close your own loop.

Then actually work

The claim is worthless without a PR.

Fork, branch, small diff: first pull request guide. Stay for review. If nobody looks, wait and bump once — that page, not this one.

Hunt the next ticket on a live list, not by spraying comments:

How to pick an issue that will get merged — specified, unclaimed, recent maintainer reply.
First pull request guide — fork, branch, open the PR after you claimed.
How to respond to code review — they already commented on the diff.
What to do when your PR is ignored — green CI, wait, one bump, leave.

FAQ

How long do I wait after the comment before I start coding? If they asked you to wait for assignment, wait. If they did not, start. A day of silence is not a veto.

Can I assign myself? Only when the project says so, or the UI actually lets contributors do it. Forbidden self-assign is worse than no assignee.

Someone claimed it three months ago with no PR. Leave that thread. Pick a different unclaimed issue. Do not add the ninth “I can take this if they don’t.”

They never replied to my claim. Open the PR if the issue was already specified. A claim is not a permission slip on a public bug. If CONTRIBUTING said wait, wait.

Should I comment “is anyone working on this?” first? No. Read the thread. If it is free, state you are taking it. That question is noise.

The job is: one short claim, respect existing owners, do not self-assign where it is forbidden, then work. That is the whole page.