Use refs from CLI args rather than check against master about commitsar

[fallion]

Hi,
Definitely doable. Putting on my todo list for this week.

[Multiply]

I'll test it again today.

[fallion]

Hi @Multiply,

This has now been merged into upstream. Can you give it a try? https://github.com/outillage/commitsar#flags

Sorry about the delay.

[Multiply]

@fallion I'll test it right away.

[Multiply]

@fallion it seems like the order of the SHA's are reversed.

The first SHA should be the base, and the second SHA should be the newest commit that was merged in, for example.

[fallion]

I see now. Will flip it so it maintains the same usage as git log.

[fallion]

Flipped them. Let me know any other issues @Multiply

[Multiply]

With your latest released version, I am getting:

$ commitsar 5cf43d427b3eca3b51d74a6532920051f6085535...596a90ce88553ab60f165ec6c2239777dd45d557
unknown command "5cf43d427b3eca3b51d74a6532920051f6085535...596a90ce88553ab60f165ec6c2239777dd45d557" for "commitsar"

[fallion]

Going to investigate and add further regression tests.

[fallion]

Yes. This is a regression. Adding #176 disabled the CLI args. Will make a change in #168 to be a flag rather than a command.

[fallion]

Regression fixed in latest master. Let me know if any more adjustments are needed for your use case.

[fallion]

Hi @Multiply, was the issue fixed? Just so I know whether to close this issue.

[Multiply]

@fallion Seems to work as expected. Thanks!