-
-
Notifications
You must be signed in to change notification settings - Fork 259
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
Could you release major version(s) of your GitHub action? #137
Comments
Hey @jmfayard, I will be releasing a major version pretty soon. It's been long overdue and should address many of the existing issues in the Action. |
Note: in practice this is done by pushing a tag git tag -fa v1 -m "Update v1 tag"
git push origin v1 --force |
Hi, this is great to hear, can you please include an argument to locate a Dockerfile in a subdirectory? I looked at source and couldn't find that. |
🎉
Le ven. 17 juin 2022 à 19:49, AkhileshNS ***@***.***> a
écrit :
… Hey @jmfayard <https://github.com/jmfayard>, I will be releasing a major
version pretty soon. It's been long overdue and should address many of the
existing issues in the Action.
—
Reply to this email directly, view it on GitHub
<#137 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADQFSD3E5I2PIMXT2BI6P3VPS3CZANCNFSM5ZCQ2O6Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
This reverts commit 7ab1a3d. Due to: AkhileshNS/heroku-deploy#137
Bonjour! 🇫🇷
I contribute to GitHub Actions Kotlin DSL which provides an alternative to write GitHub Actions not in YAML but in a type-safe programming language: Kotlin.
To this end we provide type-safe wrappers for currently 72 (and counting) wrapper actions. Those type-safe wrappers are generated from its
action.yml
which we update when it goes to a new major version, for exampleactions/cache@v2
toactions/cache@v3
And of course we support your action as well!
Unfortunately when an action don't have a major version, which is what GitHub recommands, we are forced to update manually for every minor version, like from
appleboy/scp-action/v0.1.2
toappleboy/scp-action/v0.1.3
See our issue here
Would you consider creating a major version for your action?
That would make our life easier, and the life of your users easier in general.
You can find here the recommendations from GitHub:
https://github.com/actions/toolkit/blob/main/docs/action-versioning.md
(see Recommendations in particular)
The text was updated successfully, but these errors were encountered: