GITHUB-FOUNDATIONS practice question 14 of 15

What are some scenarios that can automatically subscribe you to conversations on GitHub? (Each answer presents a complete solution. Choose three.)

Full set: 75 questions
Answer options
A: Pushing a commit to the default branch
B: Being added as a repo admin
C: Opening a pull request or issue Correct answer
D: Commenting on a thread Correct answer
E: Being assigned to an issue or pull request Correct answer
Correct Answer:
C. Opening a pull request or issue; D. Commenting on a thread; E. Being assigned to an issue or pull request
Explanation

GitHub automatically subscribes a user to a conversation (thread) whenever the user 1) opens the issue or pull request, 2) comments in that thread, or 3) is assigned to the issue or pull request. In each of these events, GitHub adds the user to the thread’s “Participants” list and the user begins receiving notifications until they manually unsubscribe. No automatic subscription occurs merely from pushing code or obtaining repository-level permissions.

Why Incorrect

A. Pushing to any branch does not change thread-level subscription; only references (@mentions, commits that close issues) may generate single notifications.
B. Repository admin rights alter permissions but do not auto-enroll the user on every issue/PR conversation.

References

1. GitHub Docs – “About notifications” → Section: “Automatically watching and subscribing” (docs.github.com, rev. 2023-10-12).

2. GitHub Docs – “Managing subscriptions” → Sub-section: “Reasons you’re subscribed” ¶3–¶6 (docs.github.com/en/account-and-profile/managing-subscriptions-and-notifications-on-github).

3. Pro Git, 2nd ed., Ch. 9 “GitHub – Social Coding”, section “Notifications” pp. 231-232 (Apress, 2014, ISBN 9781484200773).

Scroll to Top