Conversation
2 new workflows are added: - `ci.yml`: Runs the linter and executes the tests to ensure that code is in proper state. Runs on each PR and during the release. - `release.yml`: Runs the integrity checks explained above and creates a release archive containing the binary, and the checksum of the current version. It then creates a new Github release and attaches these artifacts to it. Signed-off-by: acikgozb <acikgozb@proton.me>
The default Cargo "release" profile is updated to optimize the compiled binary. Also, additional metadata is added for the project. Signed-off-by: acikgozb <acikgozb@proton.me>
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
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.
2 new workflows are added:
ci.yml: Runs the linter and executes the tests to ensure that code is in proper state. Runs on each PR and during the release.release.yml: Runs the integrity checks explained above and creates a release archive containing the binary, and the checksum of the current version. It then creates a new Github release and attaches these artifacts to it.These pipelines are using the helper
execscript defined in here.Additionally, the default "release" profile of Cargo is updated to optimize the release binary.