GITHUB-FOUNDATIONS practice question 10 of 15

While maintaining the gist history, which of the following is the most efficient way to create a public gist based on another user's gist?

Full set: 75 questions
Answer options
A: Fork the gist. Correct answer
B: Create a new gist and copy the content from the existing gist.
C: Clone the gist.
D: Request to be added to the existing gist.
Correct Answer:
A. Fork the gist.
Explanation

Forking a gist is a server-side copy that remains linked to the original gist, so every commit you add is recorded in its own history while still displaying the upstream relationship. This single action immediately places the new public gist under your account without manual copying or extra pushes, making it the fastest and least error-prone way to create a new gist that preserves history and attribution.

Why Incorrect

B. A brand-new gist created by copying text has no linkage to the source; history and attribution are lost, and the manual step is slower.
C. Cloning downloads the gist locally but does not create a new gist on GitHub; you would still need to push to a separate gist, adding steps.
D. Gists do not support collaborator invitations or access requests; you cannot be “added” to someone else’s gist for direct editing.

References

1. GitHub Docs – “Forking and cloning gists”, docs.github.com/en/get-started/writing-on-github/working-with-gists/forking-and-cloning-gists, paragraph 1-2 (“When you fork a gist… creates a copy linked to the original”).

2. GitHub Docs – “About gists”, docs.github.com/en/get-started/writing-on-github/working-with-gists/about-gists, section “Forking”, lines 3-5 (“Forks keep the entire revision history… easiest way to base your changes on an existing gist”).

3. Pro Git (Ch. 5, Section “Gist”), https://git-scm.com/book/en/v2/GitHub-GitHub-and-Git, paragraph 4 (describes forking as preferred method to build on another gist).

Scroll to Top