Git Solution: Professional (EN)

This solution guide belongs to the assessment Professional. It does not provide one rigid answer; it defines verifiable answer criteria.

Grading Rubric

Area	Expectation
Terms	Working tree, index, commit, reference and remote are separated cleanly.
Evidence	Answers mention concrete commands and interpretable outputs.
Team impact	Shared history, force push, rebase and tags are classified.
Security	Credentials, signatures, hooks and secret leaks are assessed.

Sample Criteria

Solution 01: Workflows

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

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

Solution 02: Release-Strategien

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

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

Solution 03: Submodule

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

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

Solution 04: Worktrees

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

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

Solution 05: Bisect

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

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

Solution 06: Hooks

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

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

Solution 07: CI-Übergabe

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

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

Solution 08: Workflows

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

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

Solution 09: Release-Strategien

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

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

Solution 10: Submodule

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

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

Solution 11: Worktrees

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

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

Solution 12: Bisect

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

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

Solution 13: Hooks

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

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

Solution 14: CI-Übergabe

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

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

Solution 15: Workflows

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

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

Solution 16: Release-Strategien

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

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

Solution 17: Submodule

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

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

Solution 18: Worktrees

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

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

Solution 19: Bisect

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

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

Solution 20: Hooks

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

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

Solution 21: CI-Übergabe

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

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

Solution 22: Workflows

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

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

Solution 23: Release-Strategien

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

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

Solution 24: Submodule

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

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

Solution 25: Worktrees

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

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

Solution 26: Bisect

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

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

Solution 27: Hooks

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

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

Solution 28: CI-Übergabe

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

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

Solution 29: Workflows

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

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

Solution 30: Release-Strategien

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

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

Solution 31: Submodule

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

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

Solution 32: Worktrees

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

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

Solution 33: Bisect

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

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

Solution 34: Hooks

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

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

Solution 35: CI-Übergabe

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

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

Solution 36: Workflows

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

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

Solution 37: Release-Strategien

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

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

Solution 38: Submodule

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

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

Solution 39: Worktrees

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

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

Solution 40: Bisect

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

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

Practice Appendix: Professional Solution

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

A001. Workflows

Task: document context and desired state and explicitly relate the observation to Workflows.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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. Release-Strategien

Task: explain index state and explicitly relate the observation to Release-Strategien.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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. Submodule

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

A004. Worktrees

Task: assess diff and patch and explicitly relate the observation to Worktrees.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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. Bisect

Task: check remote relationship and explicitly relate the observation to Bisect.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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. Hooks

Task: isolate conflict cause and explicitly relate the observation to Hooks.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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. CI-Übergabe

Task: use reflog as recovery path and explicitly relate the observation to CI-Übergabe.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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. Workflows

Task: state a team rule and explicitly relate the observation to Workflows.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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. Release-Strategien

Task: document context and desired state and explicitly relate the observation to Release-Strategien.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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. Submodule

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

A027. Worktrees

Task: read the commit graph and explicitly relate the observation to Worktrees.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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. Bisect

Task: assess diff and patch and explicitly relate the observation to Bisect.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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. Hooks

Task: check remote relationship and explicitly relate the observation to Hooks.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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. CI-Übergabe

Task: isolate conflict cause and explicitly relate the observation to CI-Übergabe.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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. Workflows

Task: write down rollback or recovery path and explicitly relate the observation to Workflows.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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. Release-Strategien

Task: state a team rule and explicitly relate the observation to Release-Strategien.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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. Submodule

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

A050. Worktrees

Task: explain index state and explicitly relate the observation to Worktrees.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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. Bisect

Task: read the commit graph and explicitly relate the observation to Bisect.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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. Hooks

Task: assess diff and patch and explicitly relate the observation to Hooks.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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. CI-Übergabe

Task: check remote relationship and explicitly relate the observation to CI-Übergabe.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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. Workflows

Task: describe signature or hook boundary and explicitly relate the observation to Workflows.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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. Release-Strategien

Task: write down rollback or recovery path and explicitly relate the observation to Release-Strategien.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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. Submodule

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

A073. Worktrees

Task: document context and desired state and explicitly relate the observation to Worktrees.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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. Bisect

Task: explain index state and explicitly relate the observation to Bisect.
Evidence: Write down at least one Git command, one expected result and one limit of that evidence.
Team question: What coordination is required before this change lands in a shared branch?
Security question: Which credentials, signatures, hooks 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 Solution: Professional (EN)

Grading Rubric

Sample Criteria

Solution 01: Workflows

Solution 02: Release-Strategien

Solution 03: Submodule

Solution 04: Worktrees

Solution 05: Bisect

Solution 06: Hooks

Solution 07: CI-Übergabe

Solution 08: Workflows

Solution 09: Release-Strategien

Solution 10: Submodule

Solution 11: Worktrees

Solution 12: Bisect

Solution 13: Hooks

Solution 14: CI-Übergabe

Solution 15: Workflows

Solution 16: Release-Strategien

Solution 17: Submodule

Solution 18: Worktrees

Solution 19: Bisect

Solution 20: Hooks

Solution 21: CI-Übergabe

Solution 22: Workflows

Solution 23: Release-Strategien

Solution 24: Submodule

Solution 25: Worktrees

Solution 26: Bisect

Solution 27: Hooks

Solution 28: CI-Übergabe

Solution 29: Workflows

Solution 30: Release-Strategien

Solution 31: Submodule

Solution 32: Worktrees

Solution 33: Bisect

Solution 34: Hooks

Solution 35: CI-Übergabe

Solution 36: Workflows

Solution 37: Release-Strategien

Solution 38: Submodule

Solution 39: Worktrees

Solution 40: Bisect

Review Checklist for Professional Solution

Practice Appendix: Professional Solution

A001. Workflows

A002. Release-Strategien

A003. Submodule

A004. Worktrees

A005. Bisect

A006. Hooks

A007. CI-Übergabe

A008. Repository

A009. Working Tree

A010. Index

A011. Commit

A012. HEAD

A013. Branch

A014. Tag

A015. Remote

A016. Refspec

A017. Merge

A018. Rebase

A019. Reflog

A020. Hook

A021. Submodule

A022. Credential Helper

A023. Object Database

A024. Workflows

A025. Release-Strategien

A026. Submodule

A027. Worktrees

A028. Bisect

A029. Hooks

A030. CI-Übergabe

A031. Repository

A032. Working Tree

A033. Index

A034. Commit

A035. HEAD