Skip to content

Day 4: add 2 flashcards to Git Fundamentals set - #1892

Open
sonawaneutkarsh wants to merge 1 commit into
The-DevOps-Daily:mainfrom
sonawaneutkarsh:hacktoberfest/day-4-flashcards
Open

sonawaneutkarsh wants to merge 1 commit into
The-DevOps-Daily:mainfrom
sonawaneutkarsh:hacktoberfest/day-4-flashcards

Conversation

@sonawaneutkarsh

Copy link
Copy Markdown

Adds 2 flashcards to the Git Fundamentals set (cardCount 18 -> 20):

  • git-19: staging part of a file with git add -p
  • git-20: finding regressions with git bisect

Part of the 8-Day Hacktoberfest Challenge (Day 4).

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 10, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-10T20:26:09.965202Z f71ec63 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f71ec63b9b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

{
"id": "git-20",
"front": "What does git bisect do?",
"back": "git bisect performs a binary search through commit history to find the commit that introduced a bug. Mark a known-bad commit (git bisect bad) and a known-good one (git bisect good); Git checks out the middle commit and you test, repeating until the culprit is found. End with git bisect reset.",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Initialize bisect and identify the good revision

When a reader follows the commands shown here with no active bisect, the workflow cannot reach the claimed midpoint: git bisect bad requires starting a session, and after adding only that step, the bare git bisect good marks the still-checked-out bad commit as good and fails because the same commit is both good and bad. I checked git bisect -h, whose usage lists git bisect start ... and git bisect (good|bad) [<rev>...]; include the start step and pass or check out the known-good revision, as demonstrated in content/guides/introduction-to-git/08-history.md:191-198.

Useful? React with 👍 / 👎.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant