> For the complete documentation index, see [llms.txt](https://devlog.joonas.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devlog.joonas.io/git-vcs/merge.md).

# Merge 커밋 메시지 수정

이미 commit한 메시지들은 `-i`, `--interactive` 옵션으로 수정할 수있다.

이 옵션으로 커밋의 위치 변경과 squash 까지 할 수 있다.

하지만 merge commit (`merge branch 'master' into 'dev'` 등) 은 보이지 않아 커밋 메시지를 수정하기가 어렵다.

{% embed url="<https://stackoverflow.com/questions/9930637/edit-a-merge-commit-with-git-rebase>" %}

`git rebase -i --rebase-merges HEAD~` 처럼 `--rebase-merges` 옵션을 붙이면 된다.

(git v2.22 이전이라면 --preserve-merges 옵션)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://devlog.joonas.io/git-vcs/merge.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.