You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The new gitlab functionality is not using the parameter --commit-depth in querying the gitlab repo for commits. In addition the defaulted value of 30 was not being used either, for the same reason.
Reproduction steps
Steps to reproduce the behavior:
Provide a --commit-depth on command line go run main.go --repo=gitlab.com/hoppr/hoppr --commit-depth 200
Counting commits there are only 20 (gitlab's default) (print out and/or debugger)
Expected behavior
As a user providing the --commit-depth, I would expect that correct number of commits being evaluated/scored. I also expect that I don't provide a value, I'd expect the documented default of 30 to be used.
The text was updated successfully, but these errors were encountered:
Describe the bug
The new gitlab functionality is not using the parameter
--commit-depth
in querying the gitlab repo for commits. In addition the defaulted value of 30 was not being used either, for the same reason.Reproduction steps
Steps to reproduce the behavior:
--commit-depth
on command linego run main.go --repo=gitlab.com/hoppr/hoppr --commit-depth 200
Expected behavior
As a user providing the
--commit-depth
, I would expect that correct number of commits being evaluated/scored. I also expect that I don't provide a value, I'd expect the documented default of 30 to be used.The text was updated successfully, but these errors were encountered: