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

[feature] Document how to use GoReleaser variables #1874

Open
gabibguti opened this issue Mar 26, 2023 · 0 comments
Open

[feature] Document how to use GoReleaser variables #1874

gabibguti opened this issue Mar 26, 2023 · 0 comments
Labels
area:go Issue related to the Go ecosystem type:documentation Improvements or additions to documentation

Comments

@gabibguti
Copy link

gabibguti commented Mar 26, 2023

Is your feature request related to a problem? Please describe.
I did not understand how to use variables such as {{ .Env.VERSION }} in SLSA GoReleaser configuration file. It was not clear to me if I need to define these variables somewhere using the suggested code, for example $(git describe --tags --always --dirty | cut -c2-) or $(echo $GITHUB_REF_NAME | cut -c2-) for {{ .Env.VERSION }}, or if they are ready to use as {{ .Env.VERSION }}. Since using directly {{ .Env.VERSION }} did not work for me, I imagine some other setup is needed, so improving the documented example usage would help.

Describe the solution you'd like
Document how to use GoReleaser variables such as {{ .Env.VERSION }} or improve the doc to show more example usages or needed setup.

Describe alternatives you've considered
None.

Additional context
None.

@gabibguti gabibguti added status:triage Issue that has not been triaged type:feature New feature or request labels Mar 26, 2023
@ianlewis ianlewis added area:go Issue related to the Go ecosystem type:documentation Improvements or additions to documentation and removed type:feature New feature or request status:triage Issue that has not been triaged labels Apr 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:go Issue related to the Go ecosystem type:documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants