💚 fix CI routes #131
Merged
💚 fix CI routes #131
Conversation
This file contains 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
|
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @mingi3314 and the rest of your teammates on |
Merge activity
|
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.
TL;DR
This PR updates the paths used in the GitHub CI workflow for building backend executables across multiple platforms (Linux, macOS, Windows).
What changed?
The paths used to reference the 'build-backend-executable.yaml' workflow file have been changed from relative to absolute.
How to test?
After this PR is merged, triggering the CI should successfully execute the
build-backend-executable.yamlworkflow with the updated absolute paths.Why make this change?
This change ensures that the CI workflow can correctly locate and run the
build-backend-executable.yamlworkflow regardless of the execution context, providing consistency and preventing potential build errors.