Skip to content

ci: check generated BoringSSL bindings before merging - #20

Merged
richard-ramos merged 5 commits into
masterfrom
ci/check-generated-bindings
Oct 5, 2026
Merged

richard-ramos merged 5 commits into
masterfrom
ci/check-generated-bindings

Conversation

@richard-ramos

@richard-ramos richard-ramos commented Sep 9, 2026 •

Copy link
Copy Markdown
Collaborator

Regenerate boringssl.nim during the required lint check and fail if it differs from the committed file. This catches source/generated-file mismatches before merging and tells contributors to run ./build.sh and 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.nim diff 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 lint is already required.

@richard-ramos
richard-ramos merged commit 3aa1c0e into master Oct 5, 2026
18 of 19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant