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 Request: Release management #22

Open
MaSven opened this issue Sep 13, 2021 · 1 comment
Open

Feature Request: Release management #22

MaSven opened this issue Sep 13, 2021 · 1 comment

Comments

@MaSven
Copy link

MaSven commented Sep 13, 2021

To better track progress and also when do I need to update my sources, it would be nice to have tagged releases in GitHub. Even tagged pre-releases would help. I'm not asking for a binary release, just a tag with the source as a tar ball under the release section. There are probably more advantages to that.

@Morl99
Copy link

Morl99 commented Oct 28, 2021

If you are willing to switch to conventional commits, take a look at my approach to releasing:
https://github.com/dbsystel/trivy-vulnerability-explorer/blob/main/.github/workflows/publish.yml

It doesn't take much to setup and works well. In your case, the publish step itself wouldn't be necessary, but you would end the workflow after creating the release and uploading the assets to it.

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