Skip to content

Tests and demonstration of some file formatting checks that may be used in continuous integration.

License

Notifications You must be signed in to change notification settings

per1234/formatting-checks

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

17 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

formatting-checks

Tests and demonstration of some file formatting checks that may be used in continuous integration.

See the "Test Formatting checks (expected to fail)" and "Test Formatting checks (expected to pass)" sections of .travis.yml and the Travis CI build log.

Scripts to correct non-compliant formatting are located in the correction-scripts folder.

Git pre-commit hooks to check for non-compliant formatting are located in the hooks folder.

Checks

  • UTF-8 BOM file encoding
  • Files starting with blank lines
  • Tabs
  • Trailing whitespace
  • Non-Unix line endings
  • Extra blank lines at end of file
  • Files that don't end in a newline

Contributing

Pull requests or issue reports are welcome! Please see the contribution rules for instructions.

About

Tests and demonstration of some file formatting checks that may be used in continuous integration.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages