Wiki workshop · Αγγλικά

Git Exercises: Professional (EN)

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

Γλώσσα περιεχομένου · ΑγγλικάΜέγεθος · 73.2 KBexercises/03-professional-exercises-git-EN.md

Παραδείγματα workshop σε ZIP

Πρόοδος μάθησης στη web app

Σημειώστε κεφάλαια ως αναγνωσμένα, δείτε την πρόοδο ανάγνωσης και ολοκληρώστε πρακτικές ενότητες αφού ενεργοποιήσετε την προαιρετική web app. Η πρόοδος του workshop υπολογίζεται από τα κεφάλαια όλων των σελίδων τεκμηρίωσης. Οι επιλογές μένουν σε αυτή τη συσκευή· δεν υπάρχει λογαριασμός ή συγχρονισμός με server. Δεν απαιτείται εγκατάσταση. Η ανάκληση στις Ρυθμίσεις απορρήτου διαγράφει την πρόοδο.

Πρόοδος ανάγνωσης0%

0%

0 / 6 κεφάλαια που διαβάστηκαν

Δεν υπάρχει ακόμη ελληνική έκδοση αυτού του εγγράφου. Το περιεχόμενο εμφανίζεται στα αγγλικά.

Άλλη γλωσσική έκδοσηΓερμανικά ↗Ελληνικά ↗

Git Exercises: Professional (EN)

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

Submission Format

Do not store production secrets. Document instead:

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

Required Tasks

Task 01: Workflows

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

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

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

Task 02: Release-Strategien

Goal: Examine Release-Strategien in an isolated Git lab and document the effect.

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

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

Task 03: Submodule

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

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

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

Task 04: Worktrees

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

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

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

Task 05: Bisect

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

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

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

Task 06: Hooks

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

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

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

Task 07: CI-Übergabe

Goal: Examine CI-Übergabe in an isolated Git lab and document the effect.

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

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

Task 08: Workflows

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

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

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

Task 09: Release-Strategien

Goal: Examine Release-Strategien in an isolated Git lab and document the effect.

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

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

Task 10: Submodule

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

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

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

Task 11: Worktrees

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

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

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

Task 12: Bisect

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

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

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

Task 13: Hooks

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

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

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

Task 14: CI-Übergabe

Goal: Examine CI-Übergabe in an isolated Git lab and document the effect.

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

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

Task 15: Workflows

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

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

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

Task 16: Release-Strategien

Goal: Examine Release-Strategien in an isolated Git lab and document the effect.

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

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

Task 17: Submodule

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

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

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

Task 18: Worktrees

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

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

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

Task 19: Bisect

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

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

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

Task 20: Hooks

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

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

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

Task 21: CI-Übergabe

Goal: Examine CI-Übergabe in an isolated Git lab and document the effect.

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

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

Task 22: Workflows

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

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

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

Task 23: Release-Strategien

Goal: Examine Release-Strategien in an isolated Git lab and document the effect.

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

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

Task 24: Submodule

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

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

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

Practice Appendix: Professional Exercises

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

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

A075. Hooks

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

A076. CI-Übergabe

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

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.

Official Sources and Scope

The material is aligned with public Git documentation. GitHub, GitLab, Forgejo and other hosting platforms are mentioned only where they explain common Git workflows; they are not the same thing as Git itself.

Git Reference: https://git-scm.com/docs
Git Manual: https://git-scm.com/docs/git
Pro Git Book: https://git-scm.com/book/en/v2
git-submodule: https://git-scm.com/docs/git-submodule
gitcredentials: https://git-scm.com/docs/gitcredentials
git-credential-store: https://git-scm.com/docs/git-credential-store
GitHub Certifications: https://docs.github.com/en/get-started/showcase-your-expertise-with-github-certifications/about-github-certifications
GitHub Foundations on Microsoft Learn: https://learn.microsoft.com/en-us/credentials/certifications/github-foundations/

Additional Review Drills

Use these drills when the primary task is complete and the learner needs another pass over operational reasoning. They are intentionally evidence-oriented and can be answered in a local lab repository.

Drill 01: working tree

State which Git state or reference is affected by working tree.
Name one command that produces evidence and one field or line in the output that matters.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared training repository.

Drill 02: index

State which Git state or reference is affected by index.
Name one command that produces evidence and one field or line in the output that matters.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared training repository.

Drill 03: commit graph

State which Git state or reference is affected by commit graph.
Name one command that produces evidence and one field or line in the output that matters.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared training repository.

Drill 04: branch reference

State which Git state or reference is affected by branch reference.
Name one command that produces evidence and one field or line in the output that matters.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared training repository.

Drill 05: remote-tracking branch

State which Git state or reference is affected by remote-tracking branch.
Name one command that produces evidence and one field or line in the output that matters.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared training repository.

Drill 06: reflog

State which Git state or reference is affected by reflog.
Name one command that produces evidence and one field or line in the output that matters.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared training repository.

Drill 07: credential helper

State which Git state or reference is affected by credential helper.
Name one command that produces evidence and one field or line in the output that matters.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared training repository.

Drill 08: signature

State which Git state or reference is affected by signature.
Name one command that produces evidence and one field or line in the output that matters.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared training repository.

Drill 09: hook

State which Git state or reference is affected by hook.
Name one command that produces evidence and one field or line in the output that matters.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared training repository.

Drill 10: submodule

State which Git state or reference is affected by submodule.
Name one command that produces evidence and one field or line in the output that matters.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared training repository.

Drill 11: tag

State which Git state or reference is affected by tag.
Name one command that produces evidence and one field or line in the output that matters.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared training repository.

Drill 12: recovery

State which Git state or reference is affected by recovery.
Name one command that produces evidence and one field or line in the output that matters.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared training repository.

Drill 13: working tree

State which Git state or reference is affected by working tree.
Name one command that produces evidence and one field or line in the output that matters.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared training repository.

Drill 14: index

State which Git state or reference is affected by index.
Name one command that produces evidence and one field or line in the output that matters.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared training repository.

Drill 15: commit graph

State which Git state or reference is affected by commit graph.
Name one command that produces evidence and one field or line in the output that matters.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared training repository.

Drill 16: branch reference

State which Git state or reference is affected by branch reference.
Name one command that produces evidence and one field or line in the output that matters.
Explain what can be concluded from that evidence and what cannot be concluded from it.
Describe the safest recovery path for a shared training repository.

GIT · Orthevs Academy

31 modules ως ενιαία διαδρομή μάθησης.

Η σειρά παραμένει αμετάβλητη: από τη βασική δομή του lab μέσω τεχνικών θεμελίων και λειτουργικών μοντέλων έως το τελικό troubleshooting. Τα τεχνικά ονόματα καταλόγων διατηρούνται σκόπιμα.

Πρακτικά modules