Do not understand "Reverse the commit"

Open
#1,966 1 comment 0 reactions 0 assignees View on GitHub

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

enhancement
General overview of your idea.

Git Tools - Advanced Merging -- Reverse the commit
image
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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from progit/progit2

All issues in progit/progit2

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.