non-production update readme target best practices - #140
Draft
omeedrj wants to merge 1 commit into
Draft
Conversation
…include best practices for process setting lookup when using targets
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
non-production update readme target best practices
Summary of Changes
FYI
This is an alternate lazy PR as I ran into issues bumping the gem's patch version in this PR #139 as it also automatically bumped theactivesupportversion to 7.1+ which is causing issues.Edit: Just kidding seems like the failures will occur on this PR too because we matrix test against rails 7.0 in CI.... going to leave these PR's open for anyone else that wants to try and dig in.
See this thread for details