Email Hook Branch Value Bug
I've noticed that emails sent out as a result of > 1 commits (in a single push), branch values EXCEPT the last commit are set to none.
This is easily reproduced by doing the following:
- Modify file1
- git add file1
- git commit -m "First commit"
- Modify file2
- git add file2
- git commit -m "Second commit"
- git push
The triggered email body content will show 2 new commits, the first of which will have a branch value as none. IF the above files were on master, only the last commit would have this value set.