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

Deployment should only work on pushing of certain tags? #3

Open
ronaldtse opened this issue Sep 9, 2022 · 4 comments
Open

Deployment should only work on pushing of certain tags? #3

ronaldtse opened this issue Sep 9, 2022 · 4 comments

Comments

@ronaldtse
Copy link

Right now, pushing any tag will result in deployment. However, we probably only want pushing a certain type of tag, e.g. 'v1.0' to trigger deployment? If someone pushes an old tag, the deployment will happen as well and that is not desired.

@strogonoff
Copy link

I support this, this helps avoid situations where someone pushes a change but forgets to increment version. Version is shown in GUI and people may rely on it in some cases, so it’s undesirable.

@strogonoff
Copy link

strogonoff commented Sep 11, 2022

relaton-py does it this way, but this service doesn’t use the v prefix for tags.

@strogonoff
Copy link

One problem here is that I don’t think Git tags are included in the PR. This creates a situation where we may have different version numbers on staging and production.

@strogonoff
Copy link

strogonoff commented Sep 11, 2022

edit: Which may be OK? Given our versions are essentially dates.

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