TL;DR: many edX tools and scripts depend upon Git commit messages so it is important that we are consistent in our usage. |
It is recommended that all developers run the following Git configuration commands:
git config --global --add branch.autosetupmerge true git config --global --add branch.autosetuprebase always git config --global --add push.default simple |
Git has an issue with files containing unicode characters in their file name on any system using HFS+ filesystem. If you use a Mac and experience an untracked file immediately upon cloning the edx-platform repo, try running the following configuration command:
git config --global core.precomposeunicode false |
When creating your own branches in shared repos, name then with your GitHub username as a prefix, separated by a slash: <username>/<description>
Even better is to use a personal fork: Working with Personal Forks. Over time, these will become more and more important.
type: subject
in 70 characters or lessBREAKING CHANGE:
footerExample commit message:
build: handle private.txt files properly The requirements/edx/private.txt file is for dev's own private package needs. There are two installation mechanisms in edx-platform, and neither handled the file properly: - `paver install_prereqs` had the wrong file name. The file was moved almost three years ago, and paver wasn't kept up. - `make requirements` used `private.*` which included private.in, which pip-sync balks at. Fixes: BOM-2345 |