Installation of copsctl via homebrew #88
Merged
Conversation
This file contains hidden or 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
|
@mochlast could you just please change your commit message prefix to "chore:" (instead of "feat:"). This prevents release-please github action to create a new release pull request. For a README change, we don't need a new copsctl release |
mochlast
force-pushed
the
feature/link-homebrew-tap
branch
from
a6b9e78 to
92be4be
Compare
|
@huf1 Done! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I created a homebrew-tap for copsctl so that installation via brew is enabled (and even tab-completion works OOTB! 😄 )
Updating the tap after a new release can and should be automated by calling the
release-prworkflow in the above repo.An example of how to dispatch a remote action can be found here