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

Proper version tagging #5

Closed
ruzickap opened this issue Feb 20, 2020 · 2 comments
Closed

Proper version tagging #5

ruzickap opened this issue Feb 20, 2020 · 2 comments

Comments

@ruzickap
Copy link
Contributor

Hello.

Would it be possible to do a proper tagging for this project please?

Maybe good starting point is here: https://github.com/actions/checkout
They are using versions like:

  • v2 -> v2.0.0
  • v1 -> v1.2.0
  • v1.1.0
  • v1.0.0

It would be really handy to use something like v1 instead of specifying the exact version only v0.0.2:

    - uses: ibiqlik/action-yamllint@v1

It will save me from changing the "exact versions" or using "master" when you release new version.

For example this project can be handy for automating the release process: https://github.com/haya14busa/action-update-semver

Thank you...

@ibiqlik
Copy link
Owner

ibiqlik commented Feb 24, 2020

Yes, agree. It needs some love around the tagging/versioning. Will get to it soon.

ibiqlik added a commit that referenced this issue Feb 28, 2020
Add wf to autotag minor and patch releases
By default use Dockerfile rather than docker image,
obviously is slower by ~15 sec which consumes precious
runner minutes but harder to automate releases, tagging and
updating image reference in action.yaml
thou not impossible. Next time.
ibiqlik added a commit that referenced this issue Feb 28, 2020
Autotag releases, use Dockerfile (for now) #5
@ibiqlik ibiqlik closed this as completed Feb 28, 2020
@ruzickap
Copy link
Contributor Author

Thank you...

PetrR

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

No branches or pull requests

2 participants