-
Notifications
You must be signed in to change notification settings - Fork 547
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[20241217] merge compatible into develop #16436
Conversation
Update code for simplified snarky interface
…ne_test_quiet_logs-package-decl Remove inline_test_quiet_logs package declaration
…snark [trivial] Transaction_snark: remove old comment reg. type constraints
…ed_prime [trivial] Pickles: document to_field_checked'
…kles-scalar-challenge [trivial] Pickles/scalar_challenge: remove old comment
!ci-build-me |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. But I have a question. The new commit checked out for snarky
does not seem to be the current master
but a commit from 11thDec. I can see you have made commits into the master branch ever since. Is that expected? Or should those other changes be also included and thus check out a6d3ccbf4e4ffdea595fc2c9bb17fbea8033fc9c instead?
|
Explain your changes:
git checkout develop && git fetch && git reset --hard origin/develop && git checkout compatible && git reset --hard origin/compatible && git checkout develop && git checkout -b dw/merge-compatible-20241217 && git merge compatible
Explain how you tested your changes:
Checklist: