Learning Goals

• Name Git states before changing anything.
• Separate working tree, index, commit graph and references.
• Distinguish local lab execution from team or remote impact.
• Store evidence in a traceable way.
• Document recovery and boundaries.

Flow

1. Open the files in the example directory.
2. Read commands.sh before executing commands blindly.
3. Run ./run.sh and inspect work/evidence/.
4. Compare log-graph.txt, status.txt, reflog.txt and branch-vv.txt.
5. Explain what would need a different decision in a real team repository.

Expected Observations

• Observation 01: Check Release-Branch, Hotfix und Tagging-Strategie and record which Git command makes the observation reliable.
• Observation 02: Check Working tree and record which Git command makes the observation reliable.
• Observation 03: Check Index and record which Git command makes the observation reliable.
• Observation 04: Check Commit graph and record which Git command makes the observation reliable.
• Observation 05: Check Branch and record which Git command makes the observation reliable.
• Observation 06: Check Remote and record which Git command makes the observation reliable.
• Observation 07: Check Reflog and record which Git command makes the observation reliable.
• Observation 08: Check Conflict resolution and record which Git command makes the observation reliable.
• Observation 09: Check Release-Branch, Hotfix und Tagging-Strategie and record which Git command makes the observation reliable.
• Observation 10: Check Working tree and record which Git command makes the observation reliable.
• Observation 11: Check Index and record which Git command makes the observation reliable.
• Observation 12: Check Commit graph and record which Git command makes the observation reliable.
• Observation 13: Check Branch and record which Git command makes the observation reliable.
• Observation 14: Check Remote and record which Git command makes the observation reliable.
• Observation 15: Check Reflog and record which Git command makes the observation reliable.
• Observation 16: Check Conflict resolution and record which Git command makes the observation reliable.
• Observation 17: Check Release-Branch, Hotfix und Tagging-Strategie and record which Git command makes the observation reliable.
• Observation 18: Check Working tree and record which Git command makes the observation reliable.
• Observation 19: Check Index and record which Git command makes the observation reliable.
• Observation 20: Check Commit graph and record which Git command makes the observation reliable.
• Observation 21: Check Branch and record which Git command makes the observation reliable.
• Observation 22: Check Remote and record which Git command makes the observation reliable.
• Observation 23: Check Reflog and record which Git command makes the observation reliable.
• Observation 24: Check Conflict resolution and record which Git command makes the observation reliable.
• Observation 25: Check Release-Branch, Hotfix und Tagging-Strategie and record which Git command makes the observation reliable.
• Observation 26: Check Working tree and record which Git command makes the observation reliable.
• Observation 27: Check Index and record which Git command makes the observation reliable.
• Observation 28: Check Commit graph and record which Git command makes the observation reliable.
• Observation 29: Check Branch and record which Git command makes the observation reliable.
• Observation 30: Check Remote and record which Git command makes the observation reliable.
• Observation 31: Check Reflog and record which Git command makes the observation reliable.
• Observation 32: Check Conflict resolution and record which Git command makes the observation reliable.
• Observation 33: Check Release-Branch, Hotfix und Tagging-Strategie and record which Git command makes the observation reliable.
• Observation 34: Check Working tree and record which Git command makes the observation reliable.
• Observation 35: Check Index and record which Git command makes the observation reliable.
• Observation 36: Check Commit graph and record which Git command makes the observation reliable.
• Observation 37: Check Branch and record which Git command makes the observation reliable.
• Observation 38: Check Remote and record which Git command makes the observation reliable.
• Observation 39: Check Reflog and record which Git command makes the observation reliable.
• Observation 40: Check Conflict resolution and record which Git command makes the observation reliable.
• Observation 41: Check Release-Branch, Hotfix und Tagging-Strategie and record which Git command makes the observation reliable.
• Observation 42: Check Working tree and record which Git command makes the observation reliable.
• Observation 43: Check Index and record which Git command makes the observation reliable.
• Observation 44: Check Commit graph and record which Git command makes the observation reliable.
• Observation 45: Check Branch and record which Git command makes the observation reliable.
• Observation 46: Check Remote and record which Git command makes the observation reliable.
• Observation 47: Check Reflog and record which Git command makes the observation reliable.
• Observation 48: Check Conflict resolution and record which Git command makes the observation reliable.
• Observation 49: Check Release-Branch, Hotfix und Tagging-Strategie and record which Git command makes the observation reliable.
• Observation 50: Check Working tree and record which Git command makes the observation reliable.
• Observation 51: Check Index and record which Git command makes the observation reliable.
• Observation 52: Check Commit graph and record which Git command makes the observation reliable.
• Observation 53: Check Branch and record which Git command makes the observation reliable.
• Observation 54: Check Remote and record which Git command makes the observation reliable.
• Observation 55: Check Reflog and record which Git command makes the observation reliable.
• Observation 56: Check Conflict resolution and record which Git command makes the observation reliable.
• Observation 57: Check Release-Branch, Hotfix und Tagging-Strategie and record which Git command makes the observation reliable.

Review Checklist for Example Release Flow Hotfix

• 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: Example Release Flow Hotfix

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

A001. Release-Branch, Hotfix und Tagging-Strategie

• Task: document context and desired state and explicitly relate the observation to Release-Branch, Hotfix und Tagging-Strategie.
• 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. Git CLI

• Task: explain index state and explicitly relate the observation to Git CLI.
• 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. Repository

• Task: read the commit graph 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.

A004. Index

• Task: assess diff and patch 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.

A005. Remote

• Task: check remote relationship 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.

A006. Credential

• Task: isolate conflict cause and explicitly relate the observation to Credential.
• 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. Recovery

• Task: use reflog as recovery path and explicitly relate the observation to Recovery.
• 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. Release-Branch, Hotfix und Tagging-Strategie

• Task: name history rewrite risk and explicitly relate the observation to Release-Branch, Hotfix und Tagging-Strategie.
• 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. Git CLI

• Task: assess credential impact and explicitly relate the observation to Git CLI.
• 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. Repository

• Task: describe signature or hook boundary 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.

A011. Index

• Task: write down rollback or recovery path 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.

A012. Remote

• Task: state a team rule 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.

A013. Credential

• Task: document context and desired state and explicitly relate the observation to Credential.
• 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. Recovery

• Task: explain index state and explicitly relate the observation to Recovery.
• 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. Release-Branch, Hotfix und Tagging-Strategie

• Task: read the commit graph and explicitly relate the observation to Release-Branch, Hotfix und Tagging-Strategie.
• 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. Git CLI

• Task: assess diff and patch and explicitly relate the observation to Git CLI.
• 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. Repository

• Task: check remote relationship 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.

A018. Index

• Task: isolate conflict cause 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.

A019. Remote

• Task: use reflog as recovery path 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.

A020. Credential

• Task: name history rewrite risk and explicitly relate the observation to Credential.
• 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. Recovery

• Task: assess credential impact and explicitly relate the observation to Recovery.
• 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. Release-Branch, Hotfix und Tagging-Strategie

• Task: describe signature or hook boundary and explicitly relate the observation to Release-Branch, Hotfix und Tagging-Strategie.
• 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. Git CLI

• Task: write down rollback or recovery path and explicitly relate the observation to Git CLI.
• 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. Repository

• Task: state a team rule 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.

A025. Index

• Task: document context and desired state 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.

A026. 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.

A027. Credential

• Task: read the commit graph and explicitly relate the observation to Credential.
• 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. Recovery

• Task: assess diff and patch and explicitly relate the observation to Recovery.
• 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. Release-Branch, Hotfix und Tagging-Strategie

• Task: check remote relationship and explicitly relate the observation to Release-Branch, Hotfix und Tagging-Strategie.
• 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. Git CLI

• Task: isolate conflict cause and explicitly relate the observation to Git CLI.
• 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. 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.

A033. Remote

• Task: assess credential impact 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.

A034. Credential

• Task: describe signature or hook boundary and explicitly relate the observation to Credential.
• 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. Recovery

• Task: write down rollback or recovery path and explicitly relate the observation to Recovery.
• 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. Release-Branch, Hotfix und Tagging-Strategie

• Task: state a team rule and explicitly relate the observation to Release-Branch, Hotfix und Tagging-Strategie.
• 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. Git CLI

• Task: document context and desired state and explicitly relate the observation to Git CLI.
• 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. Repository

• Task: explain index state 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.

A039. Index

• Task: read the commit graph 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.

A040. Remote

• Task: assess diff and patch 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.

A041. Credential

• Task: check remote relationship and explicitly relate the observation to Credential.
• 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. Recovery

• Task: isolate conflict cause and explicitly relate the observation to Recovery.
• 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. Release-Branch, Hotfix und Tagging-Strategie

• Task: use reflog as recovery path and explicitly relate the observation to Release-Branch, Hotfix und Tagging-Strategie.
• 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. Git CLI

• Task: name history rewrite risk and explicitly relate the observation to Git CLI.
• 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. Repository

• Task: assess credential impact 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.

A046. 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.

A047. Remote

• Task: write down rollback or recovery path 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.

A048. Credential

• Task: state a team rule and explicitly relate the observation to Credential.
• 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.