ci/solis #212
Merged
ci/solis #212
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kwiss
force-pushed
the
ci/solis
branch
2 times, most recently
from
13bb9ac to
36e7446
Compare
feat(dependabot): add bot for vulnerabilities ci(solis): update flow feat(ci): update trigger feat(ci): update trigger for pr ci: add missing depends on ci(solis): update ci ci(docker): update docker file feat(ci): add missing step ci(gh): only push trigger on main ci(docker): update docker ci(docker): update solis docker feat(solis): update docker file fix(cdk): update cdk ci(dockerfile): update dockerfile with dumbdata for test fix(ci): update dockerfile path ci(docker): add new solis docker image ci(cdk): update cdk add subdomain for solis staging
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
What type of PR is this? (check all applicable)
feat:)fix:)docs:)style:)refactor:)perf:)test:)build:)ci:)chore:)revert:)BREAKING CHANGE:)Related Tickets & Documents
Added tests?
Added to documentation?
[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?
PR Title and Description Guidelines:
feat:,fix:,chore:,BREAKING CHANGE:etc. in your PR title.Closing Issues