Workshop-Wiki · Englisch

Git Exercises: Advanced Security (EN)

These exercises belong to the workshop level Advanced Security. Every task requires traceable evidence: command, expected state, observed state, assessment and recovery path.

Inhaltssprache · EnglischGröße · 73.4 KBexercises/04-advanced-security-exercises-git-EN.md

Workshop-Beispiele als ZIP

Lernstand in der Web-App

Kapitel als gelesen markieren, Lesefortschritt sehen und Praxismodule abhaken: Diese Funktionen stehen nach Aktivierung der optionalen Web-App zur Verfügung. Der Workshop-Fortschritt ergibt sich automatisch aus den Kapiteln aller Dokumentseiten. Deine Auswahl bleibt auf diesem Gerät; es gibt kein Konto und keinen Serverabgleich. Eine Installation ist nicht erforderlich. Beim Widerruf in den Datenschutz-Einstellungen wird der Lernstand gelöscht.

Lesefortschritt0%

0%

0 / 6 Kapitel gelesen

Weitere SprachfassungDeutsch ↗Griechisch ↗

Git Exercises: Advanced Security (EN)

These exercises belong to the workshop level Advanced Security. Every task requires traceable evidence: command, expected state, observed state, assessment and recovery path.

Submission Format

Do not store production secrets. Document instead:

commands used,
relevant outputs,
affected Git states,
assessment of local history, shared history, remotes and credentials,
recovery or rollback path.

Required Tasks

Task 01: Signaturen

Goal: Examine Signaturen in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 02: Credentials

Goal: Examine Credentials in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 03: History Rewrite

Goal: Examine History Rewrite in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 04: Secret-Leaks

Goal: Examine Secret-Leaks in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 05: Supply Chain

Goal: Examine Supply Chain in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 06: Incident Response

Goal: Examine Incident Response in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 07: Signaturen

Goal: Examine Signaturen in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 08: Credentials

Goal: Examine Credentials in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 09: History Rewrite

Goal: Examine History Rewrite in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 10: Secret-Leaks

Goal: Examine Secret-Leaks in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 11: Supply Chain

Goal: Examine Supply Chain in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 12: Incident Response

Goal: Examine Incident Response in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 13: Signaturen

Goal: Examine Signaturen in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 14: Credentials

Goal: Examine Credentials in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 15: History Rewrite

Goal: Examine History Rewrite in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 16: Secret-Leaks

Goal: Examine Secret-Leaks in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 17: Supply Chain

Goal: Examine Supply Chain in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 18: Incident Response

Goal: Examine Incident Response in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 19: Signaturen

Goal: Examine Signaturen in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 20: Credentials

Goal: Examine Credentials in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 21: History Rewrite

Goal: Examine History Rewrite in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 22: Secret-Leaks

Goal: Examine Secret-Leaks in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 23: Supply Chain

Goal: Examine Supply Chain in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Task 24: Incident Response

Goal: Examine Incident Response in an isolated Git lab and document the effect.

Create a local lab repository or use an example in examples/.
Record git status --short --branch, git log --oneline --graph --decorate --all and, if needed, git branch -vv before the change.
Make one targeted change and explain whether working tree, index, commit graph, reference or remote is affected.
Prove the state with concrete Git output.
Describe the return path and justify why it fits local or shared history.

Success criterion: Another person can reproduce your steps and see which history was created intentionally.

Practice Appendix: Advanced Security Exercises

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

A001. Signaturen

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

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

Task: read the commit graph and explicitly relate the observation to History Rewrite.
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. Secret-Leaks

Task: assess diff and patch and explicitly relate the observation to Secret-Leaks.
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. Supply Chain

Task: check remote relationship and explicitly relate the observation to Supply Chain.
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. Incident Response

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

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

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

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

A011. HEAD

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

A012. Branch

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

A013. Tag

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

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

A015. Refspec

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

A016. Merge

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

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

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

A020. Submodule

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

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

A022. Object Database

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

A023. Signaturen

Task: write down rollback or recovery path and explicitly relate the observation to Signaturen.
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. Credentials

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

Task: document context and desired state and explicitly relate the observation to History Rewrite.
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. Secret-Leaks

Task: explain index state and explicitly relate the observation to Secret-Leaks.
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. Supply Chain

Task: read the commit graph and explicitly relate the observation to Supply Chain.
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. Incident Response

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

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

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

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

A033. HEAD

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

A034. Branch

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

A035. Tag

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

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

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

A038. Merge

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

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

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

A041. Hook

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

A042. Submodule

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

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

A044. Object Database

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

A045. Signaturen

Task: assess credential impact and explicitly relate the observation to Signaturen.
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. Credentials

Task: describe signature or hook boundary and explicitly relate the observation to Credentials.
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. History Rewrite

Task: write down rollback or recovery path and explicitly relate the observation to History Rewrite.
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. Secret-Leaks

Task: state a team rule and explicitly relate the observation to Secret-Leaks.
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. Supply Chain

Task: document context and desired state and explicitly relate the observation to Supply Chain.
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. Incident Response

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

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

A056. Branch

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

A057. Tag

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

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

A059. Refspec

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

A060. Merge

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

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

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

A063. Hook

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

A064. Submodule

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

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

A066. Object Database

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

A067. Signaturen

Task: use reflog as recovery path and explicitly relate the observation to Signaturen.
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. Credentials

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

Task: assess credential impact and explicitly relate the observation to History Rewrite.
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. Secret-Leaks

Task: describe signature or hook boundary and explicitly relate the observation to Secret-Leaks.
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. Supply Chain

Task: write down rollback or recovery path and explicitly relate the observation to Supply Chain.
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. Incident Response

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

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

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

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

A077. HEAD

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

A078. Branch

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

A079. Tag

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

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

A081. Refspec

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

A082. Merge

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

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

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

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.

GIT · Orthevs Academy

31 Module als durchgängiger Lernpfad.

Die Reihenfolge bleibt unverändert: von der Laborgrundstruktur über fachliche Grundlagen und Betriebsmodelle bis zum abschließenden Troubleshooting. Die technischen Verzeichnisnamen werden bewusst beibehalten.