Updated Publish Action #53
Merged
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
copied from the revised common styles gem's main action and updated to reflect the specifics for the current json rails logger publish action as well as removed the push trigger as gem creation needs to be a manual process
reorganises targets as well as introduces the use of the `${NAME}` variable to increase portability of the approach
WARNING: open-ended dependency on `gem` (>= 0) is not recommended, use a bounded requirement, such as '~> x.y'; see https://guides.rubygems.org/specification-reference/ for help
incremented the patch digit to `4` as well as added the `.rc01` suffix
DanielCouzens
approved these changes
Aug 14, 2024
bogdanadrianmarc
approved these changes
Aug 14, 2024
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.
${NAME}variable to increase portability of the revised makefile approachN.B. This is marked as a release candidate in the version cadence as there is additional work needed to define a gem naming standard, port to it, and make stuff common across all public and private gems; not to mention then having to initiate releases on all applications which use this, and any other, gem that needs updated.