Open justinshaw opened 5 years ago
Bump!
Feature branches for me are more of a memory jog than my commit messages, so I'd love to be able to see the branch names as well :+1:
I work in a tonne of branches every day so this feature is needed for me.
I've created my own very simple version of git-standup
, called git-scrum
:
Just run:
npm install git-scrum -g
It allows you to output your last days work into the console allowing you to view what branch a particular commit was for. Just run the command:
> git-scrum
It's certainly not got all the bells and whistles git-standup
has with all the different flags, but it provides the information I need so maybe it'll help some other people who are in the same boat.
+1
+2
+1
+1 - while i appreciate the feature branch part of git-scrum
the list seems to be missing squashed commits on the main branch from my feature branches (author is me/the same). A solution that shows both is what I'm after, tracking both work on feature branches and features that I've merged.
I love this project, and I use it daily. In this daily usage, I've identified just one possible improvement: the addition of the branch name to the commit message. I work in multiple branches for different features, and need to reference the branch name in my daily standup. If
git standup
included a flag that enabled outputting the branch name before the commit (i.e.[branch_name] Commit message
), I (and hopefully others) may be able to rely ongit standup
even more comprehensively.Is this possible today and I've just missed it?