what I've picked up over the years about the stupid content tracker
Good commit messages serve at least three important purposes:
- To speed up the reviewing process.
- To find out what changed in a range of commits (e.g. for a release note).
- To help the future maintainers, say five years into the future, to find out why a particular change was made to the code or why a specific feature was added.
Structure your commit message like this:
The repository for the assignment is public and Github does not allow the creation of private forks for public repositories.
The correct way of creating a private frok by duplicating the repo is documented here.
For this assignment the commands are:
- Create a bare clone of the repository.
(This is temporary and will be removed so just do it wherever.)
git clone --bare [email protected]:usi-systems/easytrace.git