You want the team to see how a documentation change will leave main and return. Use a Mermaid Git graph as a sketch in the Markdown note.

Give the starting commit and the branch edit readable names

~~~mermaid
gitGraph
  commit id: "guide-start"
  branch note-edits
  checkout note-edits
  commit id: "update-examples"
  checkout main
  merge note-edits
~~~

These lines describe the diagram. Preview the saved note in a Mermaid-capable viewer and trace the split after guide-start.

The graph branches from guide-start on main to update-examples on note-edits.

Illustrated planning graph. The commands inside the block describe a diagram.

Check the branch that receives the merge

Follow the branch to update-examples and back to main. The checkout main line before merge note-edits determines the receiving branch. Label the graph as a proposed history. If documenting a real change, compare the picture with the actual history and merge strategy before sharing.

The merge returns to main after checkout main.

Illustrated direction check. Confirm which branch receives the merge.

Mermaid’s Git graph syntax