May 2019
Intermediate to advanced
504 pages
11h 50m
English
During the development phase, it is important—especially if you are working with a bigger team—to keep a clean history on the development and feature branches.
In an agile-managed project life cycle, the commits on a branch (either local or remote) state that tasks belong to a user story or a bug, while the branch itself may correlate with the user story or bug. Bigger, shared branches among team members can also represent a full feature. In this context, in order to decrease the amount of commits while still keeping the source code safe, instead of creating a new commit each time a change set push occurs, you can make use of the amend commit feature:
Once the commit is amended with the changes, the local commit ...
Read now
Unlock full access