Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Not including specific branches? Only run on specified branch? #353

Closed
unixb0y opened this issue Mar 7, 2020 · 2 comments · May be fixed by #357
Closed

Not including specific branches? Only run on specified branch? #353

unixb0y opened this issue Mar 7, 2020 · 2 comments · May be fixed by #357

Comments

@unixb0y
Copy link

unixb0y commented Mar 7, 2020 •
edited

Hello everybody. We have a project that we ported to Python 3 so there's a py3k branch and I'd like to get people-related stats (how many commits per person etc) regarding exactly that specific branch (from when it was started).
It looks like it's not being considered at all, since my coworker isn't listed at all in the graphic that is created when executing:

./hercules.darwin_amd64 --burndown --burndown-people repo-cache | labours -m ownership

He only started working on the project since the new branch was created and only worked on that branch which hasn't been merged with master yet.

Is this not possible with hercules? If not, are there any plans on supporting other branches than the master branch?
@vmarkovtsev
Copy link
Collaborator

This is an interesting use-case @unixb0y, thank you for trying Hercules! Indeed, the HEAD is taken by default and there is no option to specify the branch by default :(

There is a workaround for this, however. It is not super handy but it will work. First, list all the commits that you wish to analyze:

git rev-list py3k | tac > py3k_commits.txt

Second, invoke Hercules with --commits py3k_commits.txt.

This workaround is mentioned in the README below "Now something fun" 😄

I hope this helps! I guess my answer can be too late, hehe, but if you find time to check the results and provide the feedback here then I will be very grateful ❤️

@bobheadxi bobheadxi mentioned this issue Apr 5, 2020
Open
@unixb0y
Copy link
Author

unixb0y commented Apr 13, 2020

@vmarkovtsev Thanks for replying, I actually forked the repo I wanted to analyse, set the branch I needed as the master branch and ran the tool on that repo's URL :D
Yeah your answer was quite late, I needed to submit my stuff on that day tbh, but I really appreciate you still replying with what seems like a good workaround, too!

@unixb0y unixb0y closed this as completed Apr 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

pipeline: add Pipeline.Branch to define where to find CommitsHead bobheadlabs/hercules
2 participants
@vmarkovtsev @unixb0y