fix(tac-sync-issues): prepend test_automation_scripts_directory to file path for new issues #28
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
…le path for new issues When creating a new issue with a pull request, the generated_script_path was being used directly without prepending the test_automation_scripts_directory. This caused the file path to be incomplete (e.g., iosxr/file.robot instead of workspace/jobfiles/iosxr/file.robot). The existing issue update logic correctly prepended the directory, but the new issue creation logic did not. This fix aligns both code paths to use the same path construction approach. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
ChristopherJHart
deleted the
fix/tac-sync-issues-file-path-construction
branch
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.
Summary
tac-sync-issuescommand had incomplete file paths in the pull requestfileslistgenerated_script_pathwas being used directly without prependingtest_automation_scripts_directoryiosxr/file.robotinstead ofworkspace/jobfiles/iosxr/file.robotRoot Cause
When creating a new issue with a pull request, the code used
generated_script_pathdirectly:But when updating an existing issue, the code correctly prepended the base directory:
This inconsistency caused the
process-issuescommand to look for files in the wrong location.Test plan
workspace/jobfiles/prefix🤖 AI Generation Metadata