Commit as frequently and as early as possible
Waydev will not see your commit until it has been pushed to the server.
Rebasing is preferred instead of squashing commits
This allows Waydev to track historical changes individually and retroactively.
In order for Waydev to associate tickets to pull requests and commits, one of these conditions has to be met:
The ticket ID (e.g. WAY-2907) needs to be mentioned in the pull request title.
The ticket ID (e.g. WAY-2907) needs to be mentioned in the commit message.
Impose to all the engineers the practice of setting up git global configuration (a.k.a setting a global email and username)
If this is not set, then any git provider (Github, Gitlab, etc.) will create a different profile based on the workstation from which the dev works, which in turn will result in different dev profiles in Waydev, which the manager has to merge otherwise the data will be incomplete.
In order to avoid duplicate contributor profiles, engineers need to have the following commands set up in their Terminal.
git config --global user.name "FIRST_NAME LAST_NAME" git config --global user.email "[email protected]"
Not committing at the start of a feature/task will result in skewed cycle/lead time.
Cycle time is computed by summing up 4 key development intervals, one of which is coding, which is calculated by looking at the difference between when the first commit was created and when the pull request was issued. If all the commits are pushed right before the creation of the pull request, coding time will be close to 0 - managers will be very happy with their low cycle time when it should have been higher with multiple days.
Updated about 2 months ago