Automatic GitHub Conversation Subscriptions
Short answer
CDE You are automatically subscribed when opening a pull request or issue, being assigned to one, or commenting on the thread.
Question
Key Takeaways
The exam tests knowledge of GitHub's default notification behaviors, specifically trapping candidates who confuse repository administration roles with conversation-level engagement triggers.
This question explores GitHub's automatic subscription rules for issues and pull requests. The correct answers identify the specific user actions that trigger an immediate opt-in to notifications.
Common mistake: Candidates often incorrectly select 'being added as a repo admin' or 'pushing a commit', assuming broad permissions or code changes automatically subscribe users to all discussions in the repository.
Expert Analysis
Why the Answer Is Correct
GitHub automatically subscribes you to a conversation when you take direct action on it. Opening a new issue or pull request (C) registers you as the author. Being assigned to an issue or pull request (D) links your identity to the task, triggering notifications. Commenting on a thread (E) makes you an active participant. These three scenarios ensure you receive updates relevant to your direct involvement.
Why the Other Options Are Wrong
Being added as a repo admin (A) grants high-level permissions but does not automatically subscribe you to every conversation; admins must manage subscriptions separately. Pushing a commit to the default branch (B) is a code action. While it generates activity, it does not automatically subscribe you to existing issue threads unless you are already involved or have specific custom settings enabled.
Community Comment Notes
The community consensus strongly supports options C, D, and E. As Kiwi28 noted, these align with official GitHub documentation regarding automatic subscription triggers. There is no significant disagreement in the comments, confirming this is a standard behavior question.
Official Reference
This link opens the official vendor documentation in a new tab.
Exam Strategy
Focus on the distinction between 'permissions' (Admin/Owner) and 'engagement' (Author/Assignee/Commenter). For notification questions, look for actions where the user is directly interacting with the content being discussed.
Frequently Asked Questions
Does pushing a commit auto-subscribe me to issues?
Why isn't being a repo admin an automatic subscriber?
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
Kiwi28 👍 1The correct answers are C, D, and E. ✅ GitHub’s official documentation says you are automatically subscribed to a conversation when you: - C. open a pull request or issue ✅ - D. are assigned to an issue or pull request ✅ - E. comment on a thread ✅ GitHub Docs Why the others are wrong: - A. being added as a repo admin ❌ — that does not by itself subscribe you to every conversation. - B. pushing a commit to the default branch ❌ — pushing a commit does not automatically subscribe you to issue/PR conversations in general. GitHub also lists other automatic-subscription cases, such as being @mentioned, manually subscribing, or changing the state of a thread.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.