Repository navigation
chore: render Ruby issue form label - #47
Merged
redox merged 1 commit intoJul 19, 2026
Merged
Conversation
Contributor
Author
|
@leonkenneth could you review this? I picked you because the touched path history only points to Albert, so Ruby is the strongest stack signal. CI is pending. The review focus is that the issue form renders the Ruby runtime label correctly and does not change anything beyond contributor metadata. |
redox
approved these changes
Jul 19, 2026
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.
Summary
{language}placeholder in the Ruby bug-report form withRubyImpact
The change affects only the GitHub issue-form label shown to Lakehouse Ruby contributors. It restores the intended per-SDK rendering without changing the SDK API, runtime behavior, or release process.
Validation
git diff --checkThe local Ruby executable is unavailable in this environment, so YAML parsing will be covered by GitHub's workflow validation.