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

Remove requirement for release to start with 'v' #173

Merged
merged 2 commits into from
Aug 30, 2023

Conversation

CasperWA
Copy link
Collaborator

Fixes #172

The main requirement is now that the current git ref is a tag and that the tag name is a semantic version.

@CasperWA CasperWA requested a review from sygout August 29, 2023 13:16
@codecov
Copy link

codecov bot commented Aug 29, 2023

Codecov Report

Merging #173 (d1afa84) into main (174f9ee) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #173   +/-   ##
=======================================
  Coverage   71.42%   71.42%           
=======================================
  Files           9        9           
  Lines         567      567           
=======================================
  Hits          405      405           
  Misses        162      162           

Use the built-in environment variable instead of the `github` context.

This allows for one-liners.

Co-authored-by: Sylvain Gouttebroze <sylvain.gouttebroze@sintef.no>
@CasperWA CasperWA merged commit cca467e into main Aug 30, 2023
18 checks passed
@CasperWA CasperWA deleted the cwa/fix-172-too-strict-release-conditions branch August 30, 2023 07:05
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.

Too strict release tag name requirements
2 participants