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.

Sign up for GitHub

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

Jump to bottom

Do we have to replace RELEASE_VERSION ? #239

Closed
mesqueeb opened this issue Oct 17, 2022 · 2 comments
Closed

Do we have to replace RELEASE_VERSION ? #239

mesqueeb opened this issue Oct 17, 2022 · 2 comments

Comments

@mesqueeb
Copy link

with

- uses: actions/add-to-project@RELEASE_VERSION

do we have to replace RELEASE_VERSION with anything?
@mervy93
Copy link

mervy93 commented Oct 17, 2022

20220816_013632000_iOS #234

@mattcosta7
Copy link
Contributor

do we have to replace RELEASE_VERSION with anything?

You'd want to replace this most likely with the version tag or commit sha, so that you get a consistent version of this action when you run it (without the @<version> you'll always get a version from main, which could at at some point contain breaking changes).

@staycoolcall911 staycoolcall911 mentioned this issue Nov 29, 2022
Merged
MarkMcCulloh pushed a commit to winglang/wing that referenced this issue Nov 29, 2022
@staycoolcall911
fix: using a specific version for add-to-project (#800)
4745372 
Using a specific version for add-to-project as recommended by the [author of the tool](actions/add-to-project#239).
*By submitting this pull request, I confirm that my contribution is made under the terms of the 
[Monada Contribution License](https://docs.winglang.io/terms-and-policies/contribution-license.html)*.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mesqueeb @mattcosta7 @mervy93