Orthevs Orthevs Fathom new horizons
Menu

Workshop wiki · English

Git Workshop: Intermediate (EN)

This level covers Branches, Merges, Konflikte, Remotes, Tags, Stash, Rebase. You work with local Git labs from examples/, create controlled histories and document which states exist in working tree, index, commit graph, references and re…

Content language · EnglishSize · 66.5 KBworkshops/02-intermediate-git-EN.md
Workshop examples as ZIP files
Learning progress in the web app

Mark chapters as read, view reading progress and check off practice modules after enabling the optional web app. Workshop progress is calculated from chapters across all document pages. Your choices stay on this device; there is no account or server sync. Installation is not required. Withdrawing your choice in Privacy settings deletes the progress.

Reading progress0%
0%
0 / 11 chapters read
Other language versionGerman ↗Greek ↗

Git Workshop: Intermediate (EN)

Target State

This level covers Branches, Merges, Konflikte, Remotes, Tags, Stash, Rebase. You work with local Git labs from examples/, create controlled histories and document which states exist in working tree, index, commit graph, references and remotes.

01 / 11

Position in the Path

The level is part of a four-stage learning path. All exercises use disposable local repositories under work/. Production credentials, real private keys and real project histories do not belong in these labs.

02 / 11

Exercise Sheet

The practical tasks are in 02-intermediate-exercises-git-EN.md. The assessment is in 02-intermediate-git-assessment-EN.md.

03 / 11

Competencies After Completion

  • You can explain, apply, verify and safely recover Branches in a Git context.
  • You can explain, apply, verify and safely recover Merges in a Git context.
  • You can explain, apply, verify and safely recover Konflikte in a Git context.
  • You can explain, apply, verify and safely recover Remotes in a Git context.
  • You can explain, apply, verify and safely recover Tags in a Git context.
  • You can explain, apply, verify and safely recover Stash in a Git context.
  • You can explain, apply, verify and safely recover Rebase in a Git context.
04 / 11

Diagrams

Working Tree, Index and Commit

text
edit files -> git add -> index -> git commit -> commit graph

Branch and HEAD

text
refs/heads/main -> Commit C
HEAD -> refs/heads/main

Remote Synchronization

text
local branch -> push -> remote branch
remote branch -> fetch -> origin/main -> merge or rebase -> local branch
05 / 11

Practice Modules

Module 1: Check context

Focus: Branches.

  • Create or open a local lab repository.
  • Before changing anything, record git status --short --branch and a useful git log excerpt.
  • Make exactly one functional change and separate working tree, index and commit.
  • Prove state with Git output, not assumptions.
  • Explain whether restore, reset, revert, merge --abort, rebase --abort or reflog is the right return path.

Module 2: Read index and diff

Focus: Merges.

  • Create or open a local lab repository.
  • Before changing anything, record git status --short --branch and a useful git log excerpt.
  • Make exactly one functional change and separate working tree, index and commit.
  • Prove state with Git output, not assumptions.
  • Explain whether restore, reset, revert, merge --abort, rebase --abort or reflog is the right return path.

Module 3: Render commit graph

Focus: Konflikte.

  • Create or open a local lab repository.
  • Before changing anything, record git status --short --branch and a useful git log excerpt.
  • Make exactly one functional change and separate working tree, index and commit.
  • Prove state with Git output, not assumptions.
  • Explain whether restore, reset, revert, merge --abort, rebase --abort or reflog is the right return path.

Module 4: Move references

Focus: Remotes.

  • Create or open a local lab repository.
  • Before changing anything, record git status --short --branch and a useful git log excerpt.
  • Make exactly one functional change and separate working tree, index and commit.
  • Prove state with Git output, not assumptions.
  • Explain whether restore, reset, revert, merge --abort, rebase --abort or reflog is the right return path.

Module 5: Practice conflict or recovery path

Focus: Tags.

  • Create or open a local lab repository.
  • Before changing anything, record git status --short --branch and a useful git log excerpt.
  • Make exactly one functional change and separate working tree, index and commit.
  • Prove state with Git output, not assumptions.
  • Explain whether restore, reset, revert, merge --abort, rebase --abort or reflog is the right return path.

Module 6: Assess remote impact

Focus: Stash.

  • Create or open a local lab repository.
  • Before changing anything, record git status --short --branch and a useful git log excerpt.
  • Make exactly one functional change and separate working tree, index and commit.
  • Prove state with Git output, not assumptions.
  • Explain whether restore, reset, revert, merge --abort, rebase --abort or reflog is the right return path.

Module 7: Run security and team review

Focus: Rebase.

  • Create or open a local lab repository.
  • Before changing anything, record git status --short --branch and a useful git log excerpt.
  • Make exactly one functional change and separate working tree, index and commit.
  • Prove state with Git output, not assumptions.
  • Explain whether restore, reset, revert, merge --abort, rebase --abort or reflog is the right return path.

Module 8: Submit documented solution

Focus: Branches.

  • Create or open a local lab repository.
  • Before changing anything, record git status --short --branch and a useful git log excerpt.
  • Make exactly one functional change and separate working tree, index and commit.
  • Prove state with Git output, not assumptions.
  • Explain whether restore, reset, revert, merge --abort, rebase --abort or reflog is the right return path.
06 / 11

Safe Workflow

  1. Always check branch, status and remote before changing history.
  2. Separate local experiments from shared branches.
  3. Use revert for published fixes when history should be preserved.
  4. Use reset only deliberately and with awareness of the affected area.
  5. Use reflog before declaring commits lost.
  6. Do not use real tokens in credential exercises.
  7. Treat hooks as helpers, not as the only security control.
  8. Document team rules for rebase, force push and release tags.
07 / 11

Review Checklist for Intermediate Workshop

  • 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.
  • 41. check remote relationship: record which Git reference, commit, index state or remote is affected and how you prove the state.
  • 42. isolate conflict cause: record which Git reference, commit, index state or remote is affected and how you prove the state.
08 / 11

Practice Appendix: Intermediate Workshop

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

A001. Branches

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

A002. Merges

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

A003. Konflikte

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

A004. Remotes

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

A005. Tags

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

A006. Stash

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

A007. Rebase

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

A008. Repository

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

A009. Working Tree

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

A010. Index

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

A011. Commit

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

A012. HEAD

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

A013. Branch

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

A014. Tag

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

A015. Remote

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

A016. Refspec

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

A017. Merge

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

A018. Rebase

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

A019. Reflog

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

A020. Hook

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

A021. Submodule

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

A022. Credential Helper

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

A023. Object Database

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

A024. Branches

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

A025. Merges

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

A026. Konflikte

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

A027. Remotes

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

A028. Tags

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

A029. Stash

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

A030. Rebase

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

A031. Repository

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

A032. Working Tree

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

A033. Index

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

A034. Commit

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

A035. HEAD

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

A036. Branch

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

A037. Tag

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

A038. Remote

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

A039. Refspec

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

A040. Merge

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

A041. Rebase

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

A042. Reflog

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

A043. Hook

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

A044. Submodule

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

A045. Credential Helper

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

A046. Object Database

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

A047. Branches

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

A048. Merges

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

A049. Konflikte

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

A050. Remotes

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

A051. Tags

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

A052. Stash

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

A053. Rebase

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

A054. Repository

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

A055. Working Tree

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

A056. Index

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

A057. Commit

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

A058. HEAD

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

A059. Branch

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

A060. Tag

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

A061. Remote

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

A062. Refspec

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

A063. Merge

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

A064. Rebase

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

A065. Reflog

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

A066. Hook

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

A067. Submodule

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

A068. Credential Helper

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

A069. Object Database

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

A070. Branches

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

A071. Merges

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

A072. Konflikte

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

A073. Remotes

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

A074. Tags

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

A075. Stash

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

A076. Rebase

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

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

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

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

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

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

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

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

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

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

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

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

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

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

A090. 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.
09 / 11

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/
10 / 11

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.
11 / 11

GIT · Orthevs Academy

31 modules as one continuous learning path.

The sequence remains unchanged: from the lab skeleton through technical foundations and operating models to final troubleshooting. The technical directory names are deliberately preserved.

Practice modules

Orthevs as an app

Install Orthevs

The Orthevs web app can be installed on supported mobile devices and desktop browsers.

iPhone and iPad

Open Orthevs in Safari. Tap Share, then Add to Home Screen. Enable Open as Web App if offered, then tap Add.

Android

For the web app, open the browser menu and choose Install app or Add to Home screen. Confirm the installation.

Desktop browser

Open the browser menu or the install icon in the address bar, then choose Install app or Add to Dock.

Web app installation depends on your browser. If no install prompt appears, follow the browser steps shown above.