Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Assigning issues/PRs to (other) people ...

Open
  • Is something wrong?
#31 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github
Domain
developer-experience

Research direction

Start by reading the discussion about assigning GitHub issues and pull requests, the proposed GitHub API checks, and the in-progress label. Determine how assignment, the Time feature, and timer start conditions should work; the issue does not define a finished behavior.

Written by the indexing model from the issue text.

Description

discuss help wanted priority-1

If you aren't interested in "Process", please ignore this. 👍

Process discussions are for people who want work in systematic/sustainable/scalable organisations that don't cave in under the weight of their technical/process debt the moment a new person joins the team ... most "startups" don't have "time" to think about this kind of stuff. That is, they don't have "time" until they realise how much time they are wasting by not having clearly defined/agreed processes... ⌛️ 🔥 💸 😭

Assigning issues (and pull requests) to someone specific is a good way of communicating with that person that you want them to take on the task, but sadly that often not "enough".

Not "picking" on anyone in particular, but just for illustration purposes @jrans has 18 Open Issues which are _Assigned_ to him: https://github.com/issues?q=assignee%3A**jrans**+is%3Aopen

github-issues-assigned-to-jrans

Its really unclear which issue(s) someone is currently working on when others can assign issues to them... so when that person goes on holiday it can be difficult to know what is "done" if the issue is still open.

I prefer the scenario where each person is only working on one thing at a time...

But I'm absolutely guilty of having way too many issues assigned to myself ...
Maybe I should tidy up my list before bringing up this discussion... 😉

The Ticking Clock

This will only "work" once we have "Time" working.
Time will use the GitHub API to check which issues have been assigned to you and start counting as soon as something is assigned. That way we have "passive" time tracking.

We need some thought as to how this will work. e.g. we could still allow people to assign issues, but only when the person to whom the issue is assigned adds the in-progress label, the timer starts...

Dominant language
No language data
Stars
92
Forks
9
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dwyl/contributing

All issues in dwyl/contributing

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.