Positioning

This document does not invent a Git certification. Git is a free version control system with official documentation at git-scm.com; this workshop does not claim a universal official core Git certification comparable to some vendor product exams.

Important for this workshop:

• Git knowledge is part of many DevOps, cloud, software engineering and platform exams.
• GitHub certifications are GitHub-product focused and include Git fundamentals, but they are not a general core Git exam.
• Microsoft Learn describes GitHub Foundations as an exam for GitHub basics, repositories, collaboration and modern development practices.
• This workshop develops practical Git competence: local history, branching, remotes, recovery, signatures, credentials and security cases.

Competency Mapping

Preparation Without Exam Claims

1. Check current provider information directly at GitHub, Microsoft Learn or the relevant exam provider.
2. Compare their learning objectives with the workshop levels.
3. Document gaps before booking an external exam.
4. Practice real local repositories, not only vocabulary.
5. Use this workshop's assessments as internal readiness checks, not as a replacement for provider material.

Review Checklist for Git Certificate Preparation

• 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.
• 35. write down rollback or recovery path: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 36. state a team rule: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 37. document context and desired state: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 38. explain index state: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 39. read the commit graph: record which Git reference, commit, index state or remote is affected and how you prove the state.
• 40. assess diff and patch: record which Git reference, commit, index state or remote is affected and how you prove the state.

Practice Appendix: Git Certificate Preparation

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

A001. Repository

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

A002. Working Tree

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

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

A004. Commit

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

A005. Branch

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

A006. Remote

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

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

• Task: name history rewrite risk 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.

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

A010. Signatures

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

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

A012. Working Tree

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

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

A014. Commit

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

A015. Branch

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

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

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

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

A019. Credential Helper

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

A020. Signatures

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

A022. Working Tree

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

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

A024. Commit

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

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

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

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

A028. Reflog

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

A029. Credential Helper

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

A030. Signatures

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

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

A037. Rebase

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

A038. Reflog

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

A039. Credential Helper

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

A040. Signatures

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

A042. Working Tree

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

A043. Index

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

A044. Commit

• Task: name history rewrite risk 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.

A045. Branch

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

A046. Remote

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

A047. Rebase

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

A048. Reflog

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

A049. Credential Helper

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

A050. Signatures

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

A052. Working Tree

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

A053. Index

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

A054. Commit

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

A055. Branch

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

A056. Remote

• Task: name history rewrite risk 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.

A057. Rebase

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

A058. Reflog

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

A059. Credential Helper

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

A060. Signatures

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

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

A062. Working Tree

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

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

A064. Commit

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

A065. Branch

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

A066. Remote

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

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

A068. Reflog

• Task: name history rewrite risk 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.

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

A070. Signatures

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

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

A072. Working Tree

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

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

A074. Commit

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

A075. Branch

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

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

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

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

A079. Credential Helper

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

A080. Signatures

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

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

A082. Working Tree

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

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

A084. Commit

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

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

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

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.