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.

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

[RFR] Feat/compare tags #40

Merged
merged 7 commits into from
Aug 30, 2024
Merged

[RFR] Feat/compare tags #40

merged 7 commits into from
Aug 30, 2024

Conversation

nm2107
Copy link
Collaborator

@nm2107 nm2107 commented Aug 25, 2024

Be able to compare with tags.

Adds a new CLI arg to specify the tag to compare to.

Why ?

As the branch comparison behavior of ssc is using git merge-base command, it is not working when using a tag name instead of a branch name. So in order to keep this behavior and to also be able to compare tags, a new CLI arg has been introduced.

This was discussed some months ago on slack with a Knpeer which has noticed that this feature wasn't possible yet, and it is now implemented.

Usage exemple :

# to compare w/ tag v0.2.3 : 
$ ssc --cmd <your_stop_command> --base-tag v0.2.3

@nm2107 nm2107 requested review from jaljo and alexpozzi August 25, 2024 16:13
@nm2107 nm2107 merged commit f066c4d into master Aug 30, 2024
2 checks passed
@nm2107 nm2107 deleted the feat/compare-tags branch August 30, 2024 22:27
nm2107 added a commit that referenced this pull request Aug 30, 2024
optional args are provided

PR [40](#40) has
introduced a change in the default behavior of ssc. When running the
tool as usual, there was an error raised :

```
$ ssc --path <path> --cmd <stop_command>

error: a value is required for '--base-ref <BASE_REF>' but none was supplied
```

whereas it should use the base branch comparison by default (as we don't
want people who are upgrading ssc to change their CI scripts).

This commit fixes this issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants