You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We could definitely do that, but I am inclined towards having the `makefile` also format the `sol` files in that step, and check for the diff on the whole repo.
This way we would be able to also check if the sol files are not well formatted and ask the contributor to format them.
What do you think about doing this in a subsequent PR?
<!--
Please read and fill out this form before submitting your PR.
Please make sure you have reviewed our contributors guide before
submitting your
first PR.
-->
## Overview
<!--
Please provide an explanation of the PR, including the appropriate
context,
background, goal, and rationale. If there is an issue with this
information,
please provide a tl;dr and link the issue.
-->
Closes#158
## Checklist
<!--
Please complete the checklist to ensure that the PR is ready to be
reviewed.
IMPORTANT:
PRs should be left in Draft until the below checklist is completed.
-->
- [ ] New and updated code has appropriate documentation
- [ ] New and updated code has new and/or updated testing
- [ ] Required CI checks are passing
- [ ] Visual proof for any user facing features like CLI or
documentation updates
- [ ] Linked issues closed with keywords
This way we would be able to also check if the
sol
files are not well formatted and ask the contributor to format them.What do you think about doing this in a subsequent PR?
Originally posted by @sweexordious in #138 (comment)
The text was updated successfully, but these errors were encountered: