Self Assignment Practices - mini/git-brunching GitHub Wiki
Self Assignment Best Practices
When practicing self-assignment, it is important to consider how your contributions impact the rest of the team. The following best practice suggestions should help to ensure that developers all have a fair division of work.
- Each developer may only be assigned a single issue at a time.
- Issues should have only a single assignee unless explicitly discussed.
- Each developer may pick up any open issue from the team's board of issues as long as it meets the following criteria:
- The issue must be peer-reviewed
- The issue should not be blocked by another issue
- If there are any dependencies between issues, try to ensure understanding of how this will impact your work by communicating with those working on dependent issues.
- If there is any confusion with an issue you have picked up or would like to pick up, please clarify this confusion with either the author of an issue or a reviewer.
- Keep the rest of the team up to date with your progress by updating the status of your assigned work on the team's project board.
Something else to keep in mind, there are only a limited number of issues for the team, so try to be mindful of not taking on more than your fair share of work. We want to ensure that everyone is able to complete a fair amount of work.
Happy coding everyone :blush: