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

Allow to disable latest tag #23

Merged
merged 3 commits into from
Dec 1, 2020
Merged

Allow to disable latest tag #23

merged 3 commits into from
Dec 1, 2020

Conversation

crazy-max
Copy link
Member

Closes #19

@codecov
Copy link

codecov bot commented Dec 1, 2020

Codecov Report

Merging #23 (106c0fb) into master (4c2760b) will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #23   +/-   ##
=======================================
  Coverage   72.94%   72.94%           
=======================================
  Files           3        3           
  Lines          85       85           
  Branches       18       18           
=======================================
  Hits           62       62           
  Misses          6        6           
  Partials       17       17           
Impacted Files Coverage Δ
src/context.ts 92.30% <ø> (ø)
src/meta.ts 74.60% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4c2760b...106c0fb. Read the comment docs.

@crazy-max crazy-max merged commit 9de4428 into master Dec 1, 2020
@crazy-max crazy-max deleted the disable-latest branch December 1, 2020 05:29
@LongLiveCHIEF
Copy link

💯 someone else was busy over the the last day or two as well it seems! one step closer to deprecating HackerHappyHour/tagging-strategy action!

@@ -82,6 +82,12 @@ jobs:

tag-semver:
runs-on: ubuntu-latest
strategy:
fail-fast: false
matrix:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't using this matrix defeat the purpose of disabling latest since it would just do a run where it was true?

if you agree, I can submit a PR that instead of using a matrix, it uses a conditional expression for tag-latest instead of this matrix example.

Here's a in-production example of how I'm using it: https://github.com/OctoPrint/octoprint-docker/blob/master/.github/workflows/octoprint-release.yml#L75-L76

Or I could port the example from the docs of HackerHappyHour/tagging-strategy (Conditionally produce 'latest')

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@LongLiveCHIEF The ci workflow in this repo is just for testing purpose. Some sort of integration test if you want.

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.

Should 'latest' be given it's own input as a 'boolen'?
2 participants