💚 fix CI #133
Merged
💚 fix CI #133
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 change is about updating the paths used in the
backend-release.yamlworkflow file to call reusable workflows for building the backend executable on different platforms.What changed?
The paths previously pointed to the same directory, but now they point to the parent directory, indicating that the reusable workflows' location might have been changed.
How to test?
Ensure that the CI/CD pipeline runs correctly without errors related to the path changes applied in this PR. Verify that the backend is being built correctly on all specified platforms.
Why make this change?
This change ensures that the project's CI/CD workflow uses the correct paths to reusable workflows. This is imperative for the smooth execution of the CI/CD pipeline tasks and the successful build of the backend executable on different platforms.