What is the source control option used to store local changes on an instance for later application called?

What is the source control option used to store local changes on an instance for later application called?

• A. stash
• B. branch
• C. commit
• D. snapshot

Answer: (A)

Stash is the way to temporarily save your uncommitted changes so you can come back to them later. In the Source Control workflow, you might be in the middle of work and need to switch tasks; stashing stores those local edits without creating a commit, allowing you to reapply them when you’re ready. This is different from committing (which records changes into the repository), branching (which creates another line of development), or a snapshot (which is a fixed point-in-time capture, not a local save of in-progress edits).

Stash is the way to temporarily save your uncommitted changes so you can come back to them later. In the Source Control workflow, you might be in the middle of work and need to switch tasks; stashing stores those local edits without creating a commit, allowing you to reapply them when you’re ready. This is different from committing (which records changes into the repository), branching (which creates another line of development), or a snapshot (which is a fixed point-in-time capture, not a local save of in-progress edits).