-
Notifications
You must be signed in to change notification settings - Fork 8
Fix updating of image tag versions #626
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
Conversation
|
Deployment previews on netlify for branch
|
| push: | ||
| branches: | ||
| - 'main' | ||
| tags: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I deleted this by accident, but I'm not sure if this is even needed in the current workflow?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, we probably are now safely away from the "bothering to tag" workflow
| if: 1==2 | ||
| with: | ||
| path: ./repos/wbaas-deploy-staging | ||
| commit-message: 'Staging+Local: Deploy new UI image ${{ steps.docker_meta.outputs.tags }}' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a very theoretical concern, but I wonder if we want to replace the "deploy" terminology in these PRs with "update" as no automated deployment is happening, it's more of an automated update a human would then deploy.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I can see us looking at making this more meaningful as time goes by. Right now I think it will do
tarrow
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me; lets try this thing for a few days :)
Supersedes #623
Doing this on a new branch so I don't eat potential local changes from @rosalieper
Example PRs opened by this approach: