Repository navigation
ci: check generated BoringSSL bindings before merging - #20
Merged
Merged
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
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.
Regenerate
boringssl.nimduring the requiredlintcheck and fail if it differs from the committed file. This catches source/generated-file mismatches before merging and tells contributors to run./build.shand commit the result.Generation previously embedded absolute checkout paths in source comments. Normalize those comments to repository-relative paths so identical sources produce identical output in different checkouts. The large
boringssl.nimdiff removes those path prefixes and reformats the shorter comments; declarations are unchanged.Use the same Ubuntu 22.04 runner and generator dependency setup as the BoringSSL update workflow. The check runs for all PRs and merge groups; no branch-rule changes are needed because
lintis already required.