Improve formatting by using golines#69
Open
jrosain wants to merge 3 commits intoGoelandProver:masterfrom
Open
Conversation
jrosain
force-pushed
the
use-golines
branch
2 times, most recently
from
00bd793 to
853d2dd
Compare
github-actions
bot
removed
needs:ci
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Add golines to the nix environment & to the contribution guide. This allows us to format the files with lines no more than$n$ columns wide. Currently, I've set $n$ to 100, but I'm open to discussions on adjusting it.
Add an automated linter in the GitHub CI that checks if all the files are properly formatted.
I've run the CLI tool on the folder to automatically remove lines that were way too long.