git cheat sheet for Core development¶
This is a short list of commands. If you are not familiar with the workflow yet, make sure you follow the link at the beginning of each section and read the detailed description.
The following commands assume you are in the working directory of the TYPO3 core repository.
Clone latest master into current directory:
git clone git://git.typo3.org/Packages/TYPO3.CMS.git .
Details: Setting up your Git environment
Set username and email in repository configuration (default is
--local = in current repo .git/config):
git config user.name "Your Name" git config user.email "firstname.lastname@example.org"
If your username and email is the same for all your projects, set it globally (in home config ~/.gitconfig, active for all git repos):
git config --global user.name "Your Name" git config --global user.email "email@example.com"
git config branch.autosetuprebase remote
Copy commit-msg hook:
cp Build/git-hooks/commit-msg .git/hooks/commit-msg
Push to gerrit
<YOUR_TYPO3_USERNAME>with your Gerrit / typo3.org user name!
git config url."ssh://<YOUR_TYPO3_USERNAME>@review.typo3.org:29418".pushInsteadOf git://git.typo3.org
Optional: Set a commit message template:
git config commit.template ~/.gitmessage.txt
This command uses the file ~/.gitmessage.txt as git message template. For additional information about how to set up a proper commit message see Commit Template
Show current configuration:
git config -l
Workflow - common commands¶
For details see Create & submit a patch
Reset repo to last remote commit in (remote) master:
git reset --hard origin/master && git pull origin master
Stage and commit all changes:
git commit -a
Is the same as:
git add . git commit
Stage and commit all changes to already existing commit:
git commit -a --amend
Push changes to remote master on gerrit (default method):
git push origin HEAD:refs/publish/master
Workflow - drafts¶
Push changes to remote master on gerrit as draft:
git push origin HEAD:refs/drafts/master
When pushing as draft, the pushed patch will only be visible to you and those who you add as a reviewer. It also does not start any automated tests or builds on the TYPO3 testing infrastructure.
Workflow -other branches¶
Show all branches:
git branch -a
Checkout 8.7 branch:
git checkout TYPO3_8-7
Pushing to a branch other than master only makes sense if the bug only exists on that branch and does not exist on master. Backporting of a fix to a branch is done by the core team member who merges the original fix to the master branch.
Long story short: In most cases, push to master. The rest is being taken care of when time is right.
Push 8.7 branch:
git push origin HEAD:refs/publish/TYPO3_8-7
Push 7.6 branch:
git push origin HEAD:refs/publish/TYPO3_7-6
Workflow - commit msg¶
Details: Commit Message rules for TYPO3 CMS
Example commit message for a bugfix:
[BUGFIX] Subject line Description Resolves: #12345 Releases: master, 8.7
[BUGFIX] [FEATURE] [DOCS] [TASK] [!!!][FEATURE] [WIP][TASK]
- subject < 52 chars
- other lines <= 72 chars
Workflow - Undoing / fixing things¶
Throw away all changes since last commit:
git reset HEAD --hard
Unstage a file (remove file from index, but keep in working dir):
git reset <path>
Change author for last commit:
git commit --amend --author "Some Name <some@email>"
Squash last 2 commits:
This is very handy, in case you accidentally created a new commit instead of adding to an existing commit (with
git commit --amend).
- All changes have been committed or stashed
- Run the following command:git rebase -i HEAD~2
- In the editor, replace 'pick' with 'squash' in the line describing the latest commit