Grading Rubric

Sample Criteria

Solution 01: Branches

A strong answer for Branches names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 02: Merges

A strong answer for Merges names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 03: Konflikte

A strong answer for Konflikte names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 04: Remotes

A strong answer for Remotes names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 05: Tags

A strong answer for Tags names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 06: Stash

A strong answer for Stash names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 07: Rebase

A strong answer for Rebase names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 08: Branches

A strong answer for Branches names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 09: Merges

A strong answer for Merges names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 10: Konflikte

A strong answer for Konflikte names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 11: Remotes

A strong answer for Remotes names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 12: Tags

A strong answer for Tags names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 13: Stash

A strong answer for Stash names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 14: Rebase

A strong answer for Rebase names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 15: Branches

A strong answer for Branches names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 16: Merges

A strong answer for Merges names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 17: Konflikte

A strong answer for Konflikte names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 18: Remotes

A strong answer for Remotes names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 19: Tags

A strong answer for Tags names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 20: Stash

A strong answer for Stash names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 21: Rebase

A strong answer for Rebase names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 22: Branches

A strong answer for Branches names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 23: Merges

A strong answer for Merges names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 24: Konflikte

A strong answer for Konflikte names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 25: Remotes

A strong answer for Remotes names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 26: Tags

A strong answer for Tags names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 27: Stash

A strong answer for Stash names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 28: Rebase

A strong answer for Rebase names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 29: Branches

A strong answer for Branches names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 30: Merges

A strong answer for Merges names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 31: Konflikte

A strong answer for Konflikte names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 32: Remotes

A strong answer for Remotes names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 33: Tags

A strong answer for Tags names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 34: Stash

A strong answer for Stash names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 35: Rebase

A strong answer for Rebase names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 36: Branches

A strong answer for Branches names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 37: Merges

A strong answer for Merges names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 38: Konflikte

A strong answer for Konflikte names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 39: Remotes

A strong answer for Remotes names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Solution 40: Tags

A strong answer for Tags names the affected Git states, uses at least one matching evidence command, separates local and shared history and describes a concrete recovery path.

• Good evidence: git status, git diff, git log, git show, git branch -vv, git remote -v, git reflog or targeted config output.
• Common mistake: suggesting reset --hard or push --force without checking publication and team impact.
• Security expectation: no real secrets, deliberate credential helpers, traceable signature boundaries and no sole reliance on local hooks.

Review Checklist for Intermediate Solution

• 01. document context and desired state: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 02. explain index state: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 03. read the commit graph: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 04. assess diff and patch: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 05. check remote relationship: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 06. isolate conflict cause: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 07. use reflog as recovery path: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 08. name history rewrite risk: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 09. assess credential impact: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 10. describe signature or hook boundary: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 11. write down rollback or recovery path: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 12. state a team rule: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 13. document context and desired state: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 14. explain index state: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 15. read the commit graph: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 16. assess diff and patch: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 17. check remote relationship: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 18. isolate conflict cause: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 19. use reflog as recovery path: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 20. name history rewrite risk: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 21. assess credential impact: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 22. describe signature or hook boundary: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 23. write down rollback or recovery path: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 24. state a team rule: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 25. document context and desired state: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 26. explain index state: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 27. read the commit graph: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 28. assess diff and patch: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 29. check remote relationship: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 30. isolate conflict cause: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 31. use reflog as recovery path: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 32. name history rewrite risk: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 33. assess credential impact: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 34. describe signature or hook boundary: record which Git reference, commit, index state or remote is affected and how you prove the state.

Practice Appendix: Intermediate Solution

This appendix provides a backlog for longer trainings, reviews and repetition. Each task is small enough to reproduce in a local lab repository.

A001. Branches

• Task: document context and desired state and explicitly relate the observation to Branches.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A002. Merges

• Task: explain index state and explicitly relate the observation to Merges.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A003. Konflikte

• Task: read the commit graph and explicitly relate the observation to Konflikte.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A004. Remotes

• Task: assess diff and patch and explicitly relate the observation to Remotes.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A005. Tags

• Task: check remote relationship and explicitly relate the observation to Tags.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A006. Stash

• Task: isolate conflict cause and explicitly relate the observation to Stash.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A007. Rebase

• Task: use reflog as recovery path and explicitly relate the observation to Rebase.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A008. Repository

• Task: name history rewrite risk and explicitly relate the observation to Repository.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A009. Working Tree

• Task: assess credential impact and explicitly relate the observation to Working Tree.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A010. Index

• Task: describe signature or hook boundary and explicitly relate the observation to Index.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A011. Commit

• Task: write down rollback or recovery path and explicitly relate the observation to Commit.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A012. HEAD

• Task: state a team rule and explicitly relate the observation to HEAD.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A013. Branch

• Task: document context and desired state and explicitly relate the observation to Branch.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A014. Tag

• Task: explain index state and explicitly relate the observation to Tag.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A015. Remote

• Task: read the commit graph and explicitly relate the observation to Remote.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A016. Refspec

• Task: assess diff and patch and explicitly relate the observation to Refspec.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A017. Merge

• Task: check remote relationship and explicitly relate the observation to Merge.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A018. Rebase

• Task: isolate conflict cause and explicitly relate the observation to Rebase.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A019. Reflog

• Task: use reflog as recovery path and explicitly relate the observation to Reflog.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A020. Hook

• Task: name history rewrite risk and explicitly relate the observation to Hook.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A021. Submodule

• Task: assess credential impact and explicitly relate the observation to Submodule.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A022. Credential Helper

• Task: describe signature or hook boundary and explicitly relate the observation to Credential Helper.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A023. Object Database

• Task: write down rollback or recovery path and explicitly relate the observation to Object Database.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A024. Branches

• Task: state a team rule and explicitly relate the observation to Branches.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A025. Merges

• Task: document context and desired state and explicitly relate the observation to Merges.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A026. Konflikte

• Task: explain index state and explicitly relate the observation to Konflikte.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A027. Remotes

• Task: read the commit graph and explicitly relate the observation to Remotes.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A028. Tags

• Task: assess diff and patch and explicitly relate the observation to Tags.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A029. Stash

• Task: check remote relationship and explicitly relate the observation to Stash.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A030. Rebase

• Task: isolate conflict cause and explicitly relate the observation to Rebase.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A031. Repository

• Task: use reflog as recovery path and explicitly relate the observation to Repository.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A032. Working Tree

• Task: name history rewrite risk and explicitly relate the observation to Working Tree.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A033. Index

• Task: assess credential impact and explicitly relate the observation to Index.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A034. Commit

• Task: describe signature or hook boundary and explicitly relate the observation to Commit.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A035. HEAD

• Task: write down rollback or recovery path and explicitly relate the observation to HEAD.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A036. Branch

• Task: state a team rule and explicitly relate the observation to Branch.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A037. Tag

• Task: document context and desired state and explicitly relate the observation to Tag.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A038. Remote

• Task: explain index state and explicitly relate the observation to Remote.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A039. Refspec

• Task: read the commit graph and explicitly relate the observation to Refspec.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A040. Merge

• Task: assess diff and patch and explicitly relate the observation to Merge.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A041. Rebase

• Task: check remote relationship and explicitly relate the observation to Rebase.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A042. Reflog

• Task: isolate conflict cause and explicitly relate the observation to Reflog.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A043. Hook

• Task: use reflog as recovery path and explicitly relate the observation to Hook.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A044. Submodule

• Task: name history rewrite risk and explicitly relate the observation to Submodule.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A045. Credential Helper

• Task: assess credential impact and explicitly relate the observation to Credential Helper.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A046. Object Database

• Task: describe signature or hook boundary and explicitly relate the observation to Object Database.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A047. Branches

• Task: write down rollback or recovery path and explicitly relate the observation to Branches.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A048. Merges

• Task: state a team rule and explicitly relate the observation to Merges.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A049. Konflikte

• Task: document context and desired state and explicitly relate the observation to Konflikte.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A050. Remotes

• Task: explain index state and explicitly relate the observation to Remotes.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A051. Tags

• Task: read the commit graph and explicitly relate the observation to Tags.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A052. Stash

• Task: assess diff and patch and explicitly relate the observation to Stash.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A053. Rebase

• Task: check remote relationship and explicitly relate the observation to Rebase.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A054. Repository

• Task: isolate conflict cause and explicitly relate the observation to Repository.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A055. Working Tree

• Task: use reflog as recovery path and explicitly relate the observation to Working Tree.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A056. Index

• Task: name history rewrite risk and explicitly relate the observation to Index.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A057. Commit

• Task: assess credential impact and explicitly relate the observation to Commit.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A058. HEAD

• Task: describe signature or hook boundary and explicitly relate the observation to HEAD.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A059. Branch

• Task: write down rollback or recovery path and explicitly relate the observation to Branch.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A060. Tag

• Task: state a team rule and explicitly relate the observation to Tag.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A061. Remote

• Task: document context and desired state and explicitly relate the observation to Remote.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A062. Refspec

• Task: explain index state and explicitly relate the observation to Refspec.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A063. Merge

• Task: read the commit graph and explicitly relate the observation to Merge.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A064. Rebase

• Task: assess diff and patch and explicitly relate the observation to Rebase.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A065. Reflog

• Task: check remote relationship and explicitly relate the observation to Reflog.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A066. Hook

• Task: isolate conflict cause and explicitly relate the observation to Hook.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A067. Submodule

• Task: use reflog as recovery path and explicitly relate the observation to Submodule.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A068. Credential Helper

• Task: name history rewrite risk and explicitly relate the observation to Credential Helper.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A069. Object Database

• Task: assess credential impact and explicitly relate the observation to Object Database.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A070. Branches

• Task: describe signature or hook boundary and explicitly relate the observation to Branches.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A071. Merges

• Task: write down rollback or recovery path and explicitly relate the observation to Merges.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A072. Konflikte

• Task: state a team rule and explicitly relate the observation to Konflikte.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A073. Remotes

• Task: document context and desired state and explicitly relate the observation to Remotes.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

A074. Tags

• Task: explain index state and explicitly relate the observation to Tags.
• Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
• Team question: What coordination is required before this change lands in a shared branch?
• Security question: Which credentials, signatures, hooks or confidential files could be affected?
• Recovery: Explain whether reflog, restore, reset, revert, merge --abort, rebase --abort or a backup is the right path.

Official Sources and Scope

The material is aligned with public Git documentation. GitHub, GitLab, Forgejo and other hosting platforms are mentioned only where they explain common Git workflows; they are not the same thing as Git itself.

• Git Reference: https://git-scm.com/docs
• Git Manual: https://git-scm.com/docs/git
• Pro Git Book: https://git-scm.com/book/en/v2
• git-submodule: https://git-scm.com/docs/git-submodule
• gitcredentials: https://git-scm.com/docs/gitcredentials
• git-credential-store: https://git-scm.com/docs/git-credential-store
• GitHub Certifications: https://docs.github.com/en/get-started/showcase-your-expertise-with-github-certifications/about-github-certifications
• GitHub Foundations on Microsoft Learn: https://learn.microsoft.com/en-us/credentials/certifications/github-foundations/

Additional Review Drills

Use these drills when the primary task is complete and the learner needs another pass over operational reasoning. They are intentionally evidence-oriented and can be answered in a local lab repository.

Drill 01: working tree

• State which Git state or reference is affected by working tree.
• Name one command that produces evidence and one field or line in the output that matters.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared training repository.

Drill 02: index

• State which Git state or reference is affected by index.
• Name one command that produces evidence and one field or line in the output that matters.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared training repository.

Drill 03: commit graph

• State which Git state or reference is affected by commit graph.
• Name one command that produces evidence and one field or line in the output that matters.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared training repository.

Drill 04: branch reference

• State which Git state or reference is affected by branch reference.
• Name one command that produces evidence and one field or line in the output that matters.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared training repository.

Drill 05: remote-tracking branch

• State which Git state or reference is affected by remote-tracking branch.
• Name one command that produces evidence and one field or line in the output that matters.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared training repository.

Drill 06: reflog

• State which Git state or reference is affected by reflog.
• Name one command that produces evidence and one field or line in the output that matters.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared training repository.

Drill 07: credential helper

• State which Git state or reference is affected by credential helper.
• Name one command that produces evidence and one field or line in the output that matters.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared training repository.

Drill 08: signature

• State which Git state or reference is affected by signature.
• Name one command that produces evidence and one field or line in the output that matters.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared training repository.

Drill 09: hook

• State which Git state or reference is affected by hook.
• Name one command that produces evidence and one field or line in the output that matters.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared training repository.

Drill 10: submodule

• State which Git state or reference is affected by submodule.
• Name one command that produces evidence and one field or line in the output that matters.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared training repository.

Drill 11: tag

• State which Git state or reference is affected by tag.
• Name one command that produces evidence and one field or line in the output that matters.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared training repository.

Drill 12: recovery

• State which Git state or reference is affected by recovery.
• Name one command that produces evidence and one field or line in the output that matters.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared training repository.

Drill 13: working tree

• State which Git state or reference is affected by working tree.
• Name one command that produces evidence and one field or line in the output that matters.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared training repository.

Drill 14: index

• State which Git state or reference is affected by index.
• Name one command that produces evidence and one field or line in the output that matters.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared training repository.

Drill 15: commit graph

• State which Git state or reference is affected by commit graph.
• Name one command that produces evidence and one field or line in the output that matters.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared training repository.

Drill 16: branch reference

• State which Git state or reference is affected by branch reference.
• Name one command that produces evidence and one field or line in the output that matters.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared training repository.