[REVERT][ruby] Stop Managing Signature Files#34
Merged
hayat01sh1da merged 2 commits intomasterfrom Apr 25, 2026
Merged
Conversation
f18656e to
844a6df
Compare
7a0234b to
b2e130d
Compare
b2e130d to
844a6df
Compare
5cd9c59 to
844a6df
Compare
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
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.
1. Target PR to Revert
2. Context
Acccording to the article shown below, signrature files should be hosted and ought not to be generated in GitHub Actions workflow because they should be static on a repository.
That is why,
bundle exec rbs-inline --output sig/generated/ .has been aborted since it generates new signature files and can make differences.3. Reference