Skip to content

Conversation

@hamishwillee
Copy link
Collaborator

The Guidelines for working on an issue suggest that users self assign if they can, and otherwise add a comment asking to be assigned.

In theory this is good - user asks to be assigned, and a core user then assigns them. Historically though this often doesn't work - you get people asking to be assigned to multiple issues, then getting assigned and doing no work. The issues then rot.

The current and well established process is that authors start work and create the cross link Fixes #<issue no.> in the PR to implicitly assign the issue.

  • The weakness in the process is that there is a window where multiple users might attempt to take the issue, and it is a little harder to see who owns the issue.
  • The benefit is that it is clear that the assignee is actually working on the issue, and you can still assign as needed etc.

This updates the process to reflect how assignment is actually handled on MDN.

@hamishwillee hamishwillee requested a review from a team as a code owner January 27, 2026 00:43
@github-actions github-actions bot added Content:Meta Content in the meta docs size/s [PR only] 6-50 LoC changed labels Jan 27, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Jan 27, 2026

Preview URLs (1 page)

External URLs (2)

URL: /en-US/docs/MDN/Community/Issues
Title: Creating and working on issues

(comment last updated: 2026-02-01 22:50:43)

Copy link
Contributor

@chrisdavidmills chrisdavidmills left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hamishwillee looks good, man; a couple of suggestions, but nothing major.

Also, while you're here, consider:

  • Fixing the grammar issue in the first numbered bullet — "If you're looking to contribute, search for issues with" should be "If you're looking to contribute, search for issues with a"
  • Adding a warning about not submitting AI slop fixes, as they waste our time as we will probably close them? Hrm, maybe this one requires more discussion.

Copy link
Contributor

@caugner caugner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM from my point of view, I'll let others approve.

hamishwillee and others added 2 commits January 28, 2026 08:07
@hamishwillee
Copy link
Collaborator Author

Thanks all for the review - I have accepted all suggestions and fixed the typo. Chris, yes, would be great to add a comment on AI slop as a separate PR.

Copy link
Contributor

@dipikabh dipikabh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for taking this on, Hamish! 🙌
I have a few rewording suggestions and a broader suggestion to adjust the step list to accommodate the current set of changes.

Copy link
Contributor

@chrisdavidmills chrisdavidmills left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good from my end.

Copy link
Contributor

@dipikabh dipikabh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work! Approving.
I'll check in on Monday to see how it shapes up.

@hamishwillee
Copy link
Collaborator Author

Thanks for the review @dipikabh - much improved. Merging.

@hamishwillee hamishwillee merged commit 912a46f into mdn:main Feb 1, 2026
7 checks passed
@hamishwillee hamishwillee deleted the assigning_issues branch February 1, 2026 22:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Content:Meta Content in the meta docs size/s [PR only] 6-50 LoC changed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants