You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
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.
bibxml-service/.github/workflows/main.yml
Line 6 in 131d6f7
The text was updated successfully, but these errors were encountered: