RHINENG-24144: Fix JOB_NAME slash issue in build_deploy.sh for GitHub…#797
Merged
kgaikwad merged 1 commit intoRedHatInsights:mainfrom Feb 19, 2026
Merged
Conversation
Reviewer's guide (collapsed on small PRs)Reviewer's GuideEscapes slashes in JOB_NAME when constructing the temporary job directory name in build_deploy.sh to avoid invalid path issues. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
LightOfHeaven1994
approved these changes
Feb 19, 2026
LightOfHeaven1994
left a comment
There was a problem hiding this comment.
Looks good @saurabhpimpalgaokar123
kgaikwad
approved these changes
Feb 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.
… Branch Source
PR Title 💥
Please title this PR with a summary of the change, along with the JIRA card number.
Suggested formats:
Feel free to remove this section from PR description once done.
Why do we need this change? 💭
Please include the context of this change here.
Documentation update? 📝
Security Checklist 🔒
Upon raising this PR please go through RedHatInsights/secure-coding-checklist
💂♂️ Checklist 🎯
ROS RHEL GitHub label usage for executing a desired test suite
Select the appropriate GitHub label to control which ROS RHEL backend tests run for this PR (Labels can be added before or after commits are pushed):
Note: Changing a Label on a PR with an already-tested commit will not trigger a new test run
Available ROS RHEL labels:
Additional 📣
Feel free to add any other relevant details such as links, notes, screenshots, here.
Summary by Sourcery
Bug Fixes: