▸case-01 I accidentally performed a hard reset on my local branch and lost several commits that were never pushed to the remote repository. What sequence of actions can I take to locate those missing commit hashes and restore my branch state safely? | pass→pass | 14,221 | 13,585 | -4% | 1 | 1 | 0% | 2,081 | 2,111 | +1% | 0 | 0 | — |
▸case-02 I am initializing a brand-new Git repository locally for a simple single-file Python project. I need the standard commands to stage 'main.py' and create the initial commit with the message 'initial commit'. | pass→pass | 3,137 | 3,999 | +27% | 1 | 1 | 0% | 526 | 1,206 | +129% | 0 | 0 | — |
▸case-03 I need to construct a GitHub Actions continuous integration workflow file located at .github/workflows/test.yml that runs pytest on every pull request targeting the main branch. | pass→pass | 9,730 | 4,711 | -52% | 1 | 1 | 0% | 1,504 | 1,385 | -8% | 0 | 0 | — |
▸case-04 I want to create an executable Git pre-commit script inside .git/hooks/pre-commit that executes 'flake8 .' and aborts the commit if errors are found. | pass→pass | 8,999 | 8,148 | -9% | 1 | 1 | 0% | 1,527 | 1,865 | +22% | 0 | 0 | — |
▸case-05 I have 5 small commits on my feature branch 'feature/login' that contain messy commit messages like 'fix typo' and 'wip'. I want to combine all 5 commits into a single clean commit with a descriptive message before opening a pull request. I am tempted to just run 'git reset --soft HEAD~5' and re-commit, but what is the standard interactive workflow to achieve this history cleanup directly from the commit list? | fail→pass | 11,429 | 9,205 | -19% | 1 | 1 | 0% | 2,212 | 2,522 | +14% | 0 | 0 | — |
▸case-06 I am actively making fixes to an earlier commit 'a1b2c3d' on my branch while developing. Instead of manually reordering commits during a later rebase, I want Git to automatically mark my new commit as a fixup for 'a1b2c3d' and automatically combine them during the rebase operation. How should I form my commit and trigger the rebase? | pass→pass | 7,563 | 6,676 | -12% | 1 | 1 | 0% | 1,447 | 1,777 | +23% | 0 | 0 | — |
▸case-07 A regression bug was reported on our main branch, but we don't know which of the last 100 commits introduced it. We know commit 'v1.0' was working and 'HEAD' is broken. Instead of manually checking out random commits, how can we systematically perform a binary search through commit history to identify the exact culprit commit? | pass→pass | 10,338 | 9,922 | -4% | 1 | 1 | 0% | 1,766 | 2,294 | +30% | 0 | 0 | — |
▸case-08 I am deep in working on a long feature branch 'feature/analytics' in my repository when an urgent high-priority bug report comes in for 'main'. I don't want to stash my dirty working directory changes or switch branches in my current workspace. How can I create a separate linked directory bound to the same repository to work on the hotfix concurrently? | pass→pass | 9,402 | 6,980 | -26% | 1 | 1 | 0% | 1,411 | 1,972 | +40% | 0 | 0 | — |
▸case-09 I previously committed both a database schema migration and an API endpoint refactor together in a single commit 'c3d4e5f' at the top of my branch. I need to break this single commit apart into two distinct sequential commits so my team can review them separately. What interactive rebase process allows breaking down this commit? | pass→pass | 13,208 | 8,052 | -39% | 1 | 1 | 0% | 1,965 | 2,101 | +7% | 0 | 0 | — |
▸case-10 A security fix was committed on 'main' as commit '9f8e7d6'. I need to apply this exact single commit onto two older release maintenance branches 'release/1.2' and 'release/1.3' without merging any other changes from 'main'. What command achieves this targeted commit transfer? | pass→pass | 4,416 | 5,851 | +32% | 1 | 1 | 0% | 838 | 1,419 | +69% | 0 | 0 | — |
▸case-11 Commit '8a7b6c5' on branch 'feature/ui' contains three file changes, but I only want to stage and apply the changes to 'src/styles.css' onto my current branch without automatically creating a commit. What flag with cherry-pick prevents automatic commit creation so I can discard unneeded file modifications before committing? | pass→pass | 6,090 | 6,368 | +5% | 1 | 1 | 0% | 1,003 | 1,541 | +54% | 0 | 0 | — |
▸case-12 My feature branch 'feature/auth' has diverged from 'main' which received several updates from colleagues. I want to incorporate the latest changes from 'main' into my branch before opening a PR. I want to maintain a linear, clean history without creating unnecessary merge commits on my feature branch. Which integration strategy should I select and execute? | pass→pass | 8,899 | 7,095 | -20% | 1 | 1 | 0% | 1,641 | 1,923 | +17% | 0 | 0 | — |
▸case-13 I accidentally ran 'git branch -D feature/checkout' and deleted my local branch before pushing it to origin. I need to find the commit hash where 'feature/checkout' was pointing right before deletion and recreate the branch at that exact state. What steps recover this deleted branch? | pass→pass | 9,079 | 10,630 | +17% | 1 | 1 | 0% | 1,496 | 2,083 | +39% | 0 | 0 | — |
▸case-14 During an interactive rebase, I made a mistake while resolving conflicts and completed the rebase, leaving my branch in an undesirable state. I want to undo the entire rebase operation and restore my branch to its exact commit state prior to running the rebase. What sequence of commands identifies the prior commit pointer and restores the branch safely? | pass→pass | 10,796 | 8,847 | -18% | 1 | 1 | 0% | 1,926 | 2,250 | +17% | 0 | 0 | — |
▸case-15 I finished developing a feature on branch 'feature/payment'. Before submitting my pull request to 'main', my team requires that all WIP commits are cleaned up, commit messages follow our convention, and the branch is rebased cleanly onto the latest 'main'. What structured step-by-step workflow should I execute to prepare this PR? | pass→pass | 12,707 | 13,317 | +5% | 1 | 1 | 0% | 2,277 | 2,561 | +12% | 0 | 0 | — |
▸case-16 A critical bug in production requires a hotfix. We need to create the fix once, commit it, and apply that fix to 'main', 'release/v2.0', and 'release/v2.1'. What is the structured workflow to create, apply, and verify this fix across all target branches? | pass→pass | 14,149 | 12,944 | -9% | 1 | 1 | 0% | 2,589 | 2,572 | -1% | 0 | 0 | — |
▸case-17 I need to run 'git bisect' automatically using an automated test script 'npm test' so that Git tests each commit in the binary search non-interactively and isolates the breaking commit on its own. How do I configure git bisect to execute this automated script? | pass→pass | 12,781 | 7,822 | -39% | 1 | 1 | 0% | 1,822 | 1,979 | +9% | 0 | 0 | — |
▸case-18 I have been using multiple git worktrees for parallel branch development. Now I have completed my tasks and want to view all active worktrees and remove a stale worktree directory located at '../project-hotfix'. What commands list and clean up these worktrees? | pass→pass | 6,136 | 5,244 | -15% | 1 | 1 | 0% | 1,048 | 1,365 | +30% | 0 | 0 | — |
▸case-19 During a rebase onto 'main', Git paused with conflict warnings in 'src/api.js'. I have manually edited 'src/api.js' to resolve the conflict markers and staged the resolved file using 'git add src/api.js'. I am tempted to run 'git commit' to finish the fix, but what command should actually be run to resume the rebase process? | pass→pass | 7,253 | 6,569 | -9% | 1 | 1 | 0% | 1,104 | 1,457 | +32% | 0 | 0 | — |
▸case-20 I started an interactive rebase with 'git rebase -i HEAD~4', but conflicts are overwhelming and I realize I made a mistake in planning. I want to cancel the rebase entirely and return my working copy and branch to the exact state before the rebase started. What command aborts the operation? | pass→pass | 5,640 | 3,872 | -31% | 1 | 1 | 0% | 959 | 1,125 | +17% | 0 | 0 | — |
▸case-21 My local branch 'feature/dashboard' and its remote counterpart 'origin/feature/dashboard' have diverged because I performed an interactive rebase locally to clean history after already pushing earlier commits. I want to update the remote branch with my cleaned local commits safely without affecting other branches. What command is used? | pass→pass | 7,172 | 5,700 | -21% | 1 | 1 | 0% | 1,076 | 1,384 | +29% | 0 | 0 | — |
▸case-22 I executed 'git cherry-pick 4a5b6c7', but encountered unexpected merge conflicts that I do not wish to resolve right now. How do I completely cancel the cherry-pick attempt and return the working tree to its state prior to running the command? | pass→pass | 5,180 | 4,682 | -10% | 1 | 1 | 0% | 891 | 1,182 | +33% | 0 | 0 | — |
▸case-23 A commit 'd4e5f6a' was pushed to the shared 'main' branch yesterday and caused issues in production. Because 'main' is a public shared branch, force-pushing or rebasing is prohibited by team policy. What command creates a new inverse commit that safely neutralizes the changes made by 'd4e5f6a'? | pass→pass | 3,682 | 3,071 | -17% | 1 | 1 | 0% | 471 | 1,148 | +144% | 0 | 0 | — |