Testing the new utility script and actions #57
Closed
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
cjsha
approved these changes
Sep 24, 2024
|
Due to weird issues merging this PR, PR #68 was merged instead, which is a carbon copy of this PR. |
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.
Utilizing the new utility script, call the same script from the Actions runs to ensure consistency between local and remote builds.
Note that the only one not connected right now is the Lychee step; there is a pre-existing action on Github that is used in the actions, so it is not necessarily the same call. However, we rely on the user as of now to download or install the lychee executable locally for themselves, so there are bound to be some differences there. It should provide enough consistency for now, and we can revisit it later if it becomes an issue.