git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Rebasing commits that have been pushed to remote

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 22, 2021, 19:34 UTC
Message-ID
<xmqqlf0cjuwx.fsf@gitster.g>
In-Reply-To
<71b51bc8-172f-48de-7c3f-cf55dc45b39a@gmail.com>
Lemuria <nekadek457@gmail.com> writes:
> How do you reword messages of commits that have been pushed to remotes
> (in this case GitHub)? Do I simply perform an interactive rebase 
> operation on the commits and simply push?

It is up to each project if it is an acceptable practice to rewind-and-rebuild a branch that has already been published, but if the projects participants are OK with it, then "'rebase -i' and 'push -f'" is how you would do it.

Previous: LemuriaNext: Lemuria
Message 2 of 7 in “Rebasing commits that have been pushed to remote”
  1. LemuriaDec 22, 2021
  2. Junio C HamanoDec 22, 2021
  3. LemuriaDec 23, 2021
  4. Erik Cervin EdinDec 26, 2021
  5. LemuriaDec 26, 2021
  6. rsbecker@nexbridge.comDec 26, 2021
  7. LemuriaDec 27, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.