-
Notifications
You must be signed in to change notification settings - Fork 61
Re-enable Forge Formatting Check in CI #37
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
Conversation
|
I agree with this. But first I need to provide better contributor documentation to people adding code know that they need to pass |
|
I'll just push up that documentation in this PR. Gimme a min. edit: all done @mudgen |
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.
Before stuffing contribution requirements inside the README, we can add a CONTRIBUTION.md file with all the related infos like your change.
This can have it's own issue if needed
|
Hi @adamgall, i've created a new Can you resolve conflicts and add you formatting doc in the We mention it in the Dev Workflow at line 75 but feel free to add a new section if needed Thanks |
|
I fixed the github action. Merging this. |
Re-enable Forge Formatting Check in CI
Summary
This PR re-enables the
forge fmt --checkstep in the GitHub Actions workflow that was previously commented out.Context
The Forge formatting check was temporarily disabled in a previous commit to unblock CI. After fixing formatting issues in the codebase (commit df942e7), we can now safely re-enable this check to maintain code formatting standards going forward.
Changes
Run Forge fmtstep in.github/workflows/test.ymlTesting
Impact
This ensures that all future code contributions maintain consistent formatting standards, improving code readability and reducing formatting-related conflicts in PRs.
Related Issue
Closes #36