-
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
Make tag
configurable
#111
Comments
Hi @smeijer! Note that this repo is more of a proof of concept, rather that an actually used project. This is because I found no mechanism to avoid watchers being explicitly notified about each release. In the context of this projects, that's really annoying... I'd like to explore if https://github.com/eine/tip/blob/master/ts/main.ts#L35 can help with avoiding it. Unfortunately, I have other priorities, and I cannot devote time to this repo ATM. Anyway, I agree that making the tag name configurable is a useful feature. Moreover, some examples can be provided about how to use the branch name for it. |
Yeah, I understand. The release spamming is an issue indeed. For me it was enough of a reason to no longer include Still grateful for your work though :) The idea behind |
Spamming issues should be fixed in the new Python version of the Action. Now, the same release is reused and the tag is force-pushed, instead of removing and creating the release each time. At the same time, the tag is now configurable through an option or environment variable. |
It would be nice if we could provide the tag name to use. Currently, it's called
tip
. I would favor a taglatest
ornightly
instead.If the tag is configurable, I can even imagine using various cronjobs with different tags.
The text was updated successfully, but these errors were encountered: