-
Notifications
You must be signed in to change notification settings - Fork 7
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
revamp the action for localstack authorship #2
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for updating the authorship! 🙇
README.md
Outdated
@@ -48,7 +48,7 @@ jobs: | |||
- uses: actions/checkout@v3 | |||
|
|||
- name: Start LocalStack | |||
uses: HarshCasper/setup-localstack@v0.1.2 | |||
uses: LocalStack/setup-localstack@v0.1.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: could be updated to v0.1.3
, for consistency with the version above
uses: LocalStack/setup-localstack@v0.1.2 | |
uses: LocalStack/setup-localstack@v0.1.3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general, how do you feel about introducing a latest
tag for this action @HarshCasper ? It would require a bit of additional effort every time we release a new version (tagging the latest release commit with the git tag latest
), but then users could simply refer to this in their pipelines:
uses: LocalStack/setup-localstack@latest
Might come in handy, especially if we anticipate that there will be more updates coming for this Action in the near future.. 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let me see how to set it up 👍
I will do this in a follow-up PR
Co-authored-by: Waldemar Hummer <waldemar.hummer@gmail.com>
Co-authored-by: Waldemar Hummer <waldemar.hummer@gmail.com>
No description provided.