https://github.com/per1234/formatting-checks

Tests and demonstration of some file formatting checks that may be used in continuous integration.
https://github.com/per1234/formatting-checks

continuous-integration formatting testing

Last synced: 9 days ago
JSON representation

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

• Host: GitHub
• URL: https://github.com/per1234/formatting-checks
• Owner: per1234
• License: mit
• Created: 2018-03-12T00:10:23.000Z (almost 7 years ago)
• Default Branch: master
• Last Pushed: 2019-06-20T10:34:02.000Z (over 5 years ago)
• Last Synced: 2025-01-11T04:55:02.604Z (16 days ago)
• Topics: continuous-integration, formatting, testing
• Language: Shell
• Size: 17.6 KB
• Stars: 0
• Watchers: 3
• Forks: 0
• Open Issues: 7
• Metadata Files:
  • Readme: README.md
  • Contributing: .github/CONTRIBUTING.md
  • License: LICENSE

Awesome Lists containing this project

README

        
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](https://github.com/per1234/formatting-checks/blob/master/.travis.yml) and the [Travis CI build log](https://travis-ci.org/per1234/formatting-checks).

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](https://github.com/per1234/formatting-checks/blob/master/.github/CONTRIBUTING.md) for instructions.