Collaborate using GitHub

During a sprint planning meeting, your team triages a backlog of open issues. The lead wants each issue to clearly show which single developer is responsible for resolving it, so that anyone viewing the issue list knows who is currently working on what. Which GitHub feature should the team use to accomplish this?

A developer is fixing a bug tracked in issue #42. They open a pull request with the fix and want the issue to close automatically the moment the pull request is merged into the default branch, without any manual follow-up. What should they do?

Your open-source project uses GitHub Discussions with a 'Q&A' category. A community member posts a question about how to configure a plugin, and several people reply. One reply from a maintainer fully solves the problem. As a maintainer, what is the recommended way to help future visitors quickly find the resolution within that discussion?

A repository maintainer notices that one open issue has grown into a lengthy back-and-forth where community members are debating the general direction of a feature, rather than reporting a specific, actionable bug. The maintainer wants to keep the actionable tracking work separate from the broader community conversation. Which action best fits GitHub's intended collaboration model?

A developer on your team complains that they are missing important updates on repositories they contribute to. They currently receive no email notifications and only check the GitHub web interface sporadically. They want GitHub to email them whenever there is activity on threads they are participating in, while still keeping notifications visible in the web inbox. Where should they go to enable email delivery for their participating notifications?

An open-source maintainer notices that many contributors are opening issues to ask general questions, share ideas, and hold community Q&A conversations that have no specific bug or actionable task. This clutters the issue tracker and makes it hard to see actual work items. Which GitHub collaboration tool should the maintainer enable and direct these conversations to?

During a busy sprint, a developer on a large open-source project wants to quickly see only the issues in a repository that are currently assigned to them and still open, without scrolling through hundreds of unrelated issues. What is the most efficient way to accomplish this on GitHub?

A developer has written a short, standalone shell script that several teammates keep asking for over chat. They want to share it in one place where colleagues can view it with syntax highlighting, comment on it, and even fork it—without creating a full repository. Which GitHub feature best fits this need?

A documentation team wants to publish their project's user guide as a browsable website hosted directly from their GitHub repository, using Markdown files they already maintain in the repo. They want the site to be publicly accessible via a github.io URL without setting up any external hosting. Which GitHub feature should they use?

Your open-source project receives many bug reports through issues, but they often lack key details like steps to reproduce, expected behavior, and environment information. This forces maintainers to spend time asking follow-up questions. Which GitHub feature should you configure to ensure contributors provide this information consistently when opening a new issue?

A developer is working on a fix for issue #128 in a repository. They open a pull request for the change and want GitHub to visually associate the pull request with issue #128 so reviewers can navigate between them, without necessarily closing the issue automatically. What is the recommended way to establish this link from the pull request?

A developer works across a dozen active repositories and is overwhelmed by the volume of notifications arriving in the GitHub notifications inbox. They want a way to organize incoming notifications so they can quickly focus on only those where they were directly mentioned, without permanently changing which repositories they watch. What should they use?

A developer watches several active repositories and receives dozens of notifications daily. During a busy sprint they want to quickly find only the notifications where a teammate specifically pulled them into a conversation using @-syntax, so they can respond before triaging everything else. Which built-in notification filter should they use in the GitHub notifications inbox?

You are not watching the entire repository, but a customer-reported issue is critical to your current sprint and you want to be notified of every new comment on that specific issue—without receiving notifications for unrelated activity across the repo. What is the most appropriate action?

A developer on a large open-source project is receiving hundreds of email notifications daily from a repository they contribute to occasionally. They only want to be notified when they are directly mentioned, assigned, or when they comment on a thread — not about every new issue or pull request. Which notification setting should they choose for that repository?

A project maintainer notices that several critical bugs and a roadmap tracking issue keep getting buried under newer, less important issues in the repository's issue list. She wants these key issues to always appear prominently at the top of the Issues tab so contributors see them first. Which GitHub feature should she use?

A developer has pushed several commits to a feature branch but the code is only half-finished. They want early visibility so teammates can follow along and comment, but they need to clearly signal that the changes are not yet ready to be merged and should not be formally reviewed or approved. What is the best way to open this pull request?

Priya has opened a pull request with a proposed fix for a payment bug. She wants a specific backend engineer, Marcus, to formally evaluate the code and either approve it or request changes before it is merged. Which GitHub feature should she use to bring Marcus into the pull request for this purpose?

A maintainer notices that pull requests submitted to their repository frequently omit details like a description of changes, testing steps, and a link to the related issue. They want every new pull request to automatically start with a consistent structure prompting contributors for this information. What should they add to the repository?

A software team wants a dedicated space within their repository where multiple contributors can collaboratively write and maintain long-form, multi-page documentation—such as architecture guides, onboarding instructions, and API references—that lives separately from the code but stays tied to the project. Which GitHub feature best fits this need?