Do not understand "Reverse the commit"
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- git
- Domain
- documentation
Research direction
Start with the Git Tools - Advanced Merging section and the explanation containing “There’s nothing in topic that isn’t already reachable from master.” Review the described commit history and the distinction between reverting and merging. Done means the documentation clearly explains why merging the topic branch does or does not add content after the revert.
Written by the indexing model from the issue text.
Description
General overview of your idea.
Git Tools - Advanced Merging -- Reverse the commit
What is the meaning of "There’s nothing in topic that isn’t already reachable from master."?
From the commit history, at commit ^M, C4 has been merged into master, although git revert has reverted to C6 state. So git merge topics doesn't merge again.
Does this mean that because the topic branch has no new content, it cannot be merged into the master?
What problem will this solve?
Have you thought about other solutions?
No response
Do you want to help with this enhancement idea?
Yes
- Dominant language
- CSS
- Stars
- 6.6k
- Forks
- 2.1k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from progit/progit2
-
Difficulty 1/5 Under an hour Newbie friendliness 87/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
AI-Agent/Queued Type/Bug
Difficulty 1/5 Under an hour Newbie friendliness 91/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
approved documentation
Difficulty 1/5 Under an hour Newbie friendliness 89/100
vitest-dev/vitest#12015 · 4 comments ·
Maintainers usually reply within 1 day
-
Pri3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
MicrosoftDocs/windows-dev-docs#6205 ·