Skip to content

Conversation

@btj
Copy link

@btj btj commented Oct 11, 2025

  • Fixes a bug in the Subtree Update action where a failed patch of the VeriFast proofs would cause an obscurely named, unhelpful commit to be added to the PR.
  • patch-verifast-proofs.sh now uses git merge-file instead of patch and can be called from anywhere
  • patch-verifast-proofs.sh now checks the updated proofs and rolls back the changes if the proof fails
  • Move the VeriFast invocation for checking a particular proof into a verify.sh script in that proof's directory. Makes the proof easier to audit.
  • Each VeriFast proof can now use a different version of VeriFast

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

- Fixes a bug in the Subtree Update action where a failed patch
  of the VeriFast proofs would cause an obscurely named, unhelpful
  commit to be added to the PR.
- patch-verifast-proofs.sh now uses `git merge-file` instead of `patch`
  and can be called from anywhere
- patch-verifast-proofs.sh now checks the updated proofs and rolls
  back the changes back if the proof fails
- Each VeriFast proof can now use a different version of VeriFast
@btj btj requested a review from a team as a code owner October 11, 2025 16:11
@feliperodri feliperodri removed their assignment Nov 27, 2025
Copy link
Member

@tautschnig tautschnig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs an update once #504 is merged as the version of VeriFast has changed.

@tautschnig tautschnig enabled auto-merge January 18, 2026 20:37
@tautschnig tautschnig added this pull request to the merge queue Jan 18, 2026
Merged via the queue into model-checking:main with commit dd1e82c Jan 18, 2026
27 checks passed
@btj btj deleted the verifast-scripts branch January 19, 2026 07:07
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.

4 participants