Some checks failed
Code scanning / CodeQL (push) Failing after 15s
Zulip production suite / Ubuntu 22.04 production build (push) Failing after 26s
Zulip production suite / Debian 12 production install with custom db name and user (push) Has been skipped
Zulip production suite / Ubuntu 22.04 production install and PostgreSQL upgrade with pgroonga (push) Has been skipped
Zulip production suite / Ubuntu 24.04 production install (push) Has been skipped
Zulip production suite / Ubuntu 26.04 production install (push) Has been skipped
Zulip production suite / Debian 13 production install (push) Has been skipped
Zulip production suite / 7.0 Version Upgrade (push) Has been skipped
Zulip production suite / 8.0 Version Upgrade (push) Has been skipped
Zulip production suite / 6.0 Version Upgrade (push) Has been skipped
Zulip production suite / 10.0 Version Upgrade (push) Has been skipped
Zulip production suite / 9.0 Version Upgrade (push) Has been skipped
Zulip production suite / 12.0 Version Upgrade (push) Has been skipped
Zulip production suite / 11.0 Version Upgrade (push) Has been skipped
GitHub Actions Security Analysis with zizmor / zizmor (push) Failing after 3s
Zulip CI / Debian 12 (Python 3.11, backend + documentation) (push) Failing after 26s
Zulip CI / Ubuntu 22.04 (Python 3.10, backend + frontend) (push) Failing after 3s
Zulip CI / Ubuntu 24.04 (Python 3.12, backend) (push) Failing after 25s
Zulip CI / Ubuntu 26.04 (Python 3.14, backend) (push) Failing after 25s
Zulip CI / Debian 13 (Python 3.13, backend) (push) Failing after 28s
Zulip production suite / Required jobs (push) Has been cancelled
Zulip CI / Required jobs (push) Has been cancelled
API Documentation Update Check / check-feature-level-updated (push) Has been cancelled
API Documentation Update Check / notify-if-api-docs-changed (push) Has been cancelled
46 lines
1.5 KiB
Markdown
46 lines
1.5 KiB
Markdown
# Fixing commits
|
|
|
|
This is mostly from
|
|
[here](https://help.github.com/en/articles/changing-a-commit-message#rewriting-the-most-recent-commit-message).
|
|
|
|
## Fixing the last commit
|
|
|
|
### Changing the last commit message
|
|
|
|
1. `git commit --amend -m "New message"`
|
|
|
|
### Changing the last commit
|
|
|
|
1. Make your changes to the files
|
|
2. Run `git add <filename>` to add one file or `git add <filename1> <filename2> ...` to add multiple files
|
|
3. `git commit --amend`
|
|
|
|
## Fixing older commits
|
|
|
|
### Changing commit messages
|
|
|
|
1. `git rebase -i HEAD~5` (if, for example, you are editing some of the last five commits)
|
|
2. For each commit that you want to change the message, change `pick` to `reword`, and save
|
|
3. Change the commit messages
|
|
|
|
### Deleting old commits
|
|
|
|
1. `git rebase -i HEAD~n` where `n` is the number of commits you are looking at
|
|
2. For each commit that you want to delete, change `pick` to `drop`, and save
|
|
|
|
## Squashing commits
|
|
|
|
Sometimes, you want to make one commit out of a bunch of commits. To do this,
|
|
|
|
1. `git rebase -i HEAD~n` where `n` is the number of commits you are interested in
|
|
2. Change `pick` to `squash` on the lines containing the commits you want to squash and save
|
|
|
|
## Reordering commits
|
|
|
|
1. `git rebase -i HEAD~n` where `n` is the number of commits you are interested in
|
|
2. Reorder the lines containing the commits and save
|
|
|
|
## Pushing commits after tidying them
|
|
|
|
1. `git push origin +my-feature-branch` (Note the `+` there and substitute your actual branch name.)
|