fix: ignore Bundler artifacts during release preparation - #53
Merged
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
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.
Release preparation rejected the checkout after ruby/setup-ruby installed gems into vendor/bundle and wrote .bundle/config. Neither generated directory was ignored.
Ignore only the root Bundler configuration and installed-gem directories. Preserve the strict clean-checkout gate. Extend the existing temporary-Git release flow test to simulate Bundler artifacts and verify that tracked edits and unrelated untracked files still stop preparation before API access.
Validation:
bundle exec fastlane android python_checkswith the pinned tooling environment passed (43 tests, Black/isort);git diff --checkpassed. No live API request or release was started. After merge, start a new release run from current main.