feat: support for running os commands as a new release action #70
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
JosephKav
force-pushed
the
32-feat-support-for-running-bash-commands-as-a-new-release-action
branch
from
8b9561d to
6fe49c0
Compare
JosephKav
force-pushed
the
32-feat-support-for-running-bash-commands-as-a-new-release-action
branch
from
6fe49c0 to
06b082b
Compare
JosephKav
force-pushed
the
master
branch
2 times, most recently
from
51a0c1c to
2e269df
Compare
JosephKav
deleted the
32-feat-support-for-running-bash-commands-as-a-new-release-action
branch
JosephKav
restored the
32-feat-support-for-running-bash-commands-as-a-new-release-action
branch
…as-a-new-release-action
JosephKav
force-pushed
the
32-feat-support-for-running-bash-commands-as-a-new-release-action
branch
3 times, most recently
from
c0ee87e to
99f52bd
Compare
JosephKav
force-pushed
the
32-feat-support-for-running-bash-commands-as-a-new-release-action
branch
from
99f52bd to
4da3021
Compare
…as-a-new-release-action
JosephKav
force-pushed
the
32-feat-support-for-running-bash-commands-as-a-new-release-action
branch
3 times, most recently
from
4cd9497 to
5a2287a
Compare
- improved tooltips to be command specific if there's no webhooks - added `ResetFails` to be used when `DeployedVersion` changes ^ so that successful commands/webhooks can be ran again on a new release
JosephKav
force-pushed
the
32-feat-support-for-running-bash-commands-as-a-new-release-action
branch
from
5a2287a to
943340b
Compare
JosephKav
force-pushed
the
32-feat-support-for-running-bash-commands-as-a-new-release-action
branch
from
26e3f65 to
0e7a068
Compare
…as-a-new-release-action
JosephKav
deleted the
32-feat-support-for-running-bash-commands-as-a-new-release-action
branch
JosephKav
added a commit
that referenced
this pull request
Jun 2, 2022
* feat: support for running commands on new release * test: command tests * feat(ui): see/approve commands * feat: show resend button when only commands are defined (no webhooks) - improved tooltips to be command specific if there's no webhooks - added `ResetFails` to be used when `DeployedVersion` changes ^ so that successful commands/webhooks can be ran again on the next new release * fix: reset webhook/command fail status on new `latestVersion` * feat(ui): show in config * fix(deployed_version): can get without `latest_version` being found
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.
Suggestion from reddit. Formatting of commands takes a bit of getting you to. You give it a command, then arguments. So to
ls -lah /tmp, you'd need to do:[ "ls", "-lah /tmp" ]doesn't workHave added
-test.commands SERVICE_NAMEthat would let you test these commandsfixes #32