zapwhite 2.10.0 → 2.11.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 2667d2750aa80378e1cbd8aa132c0e0405cc703f
-  data.tar.gz: e3068a71240dc028d0b5d088d1d12dd14d8f4aeb
+  metadata.gz: aa52754370630dbc5658dd153e3ded711c85ae25
+  data.tar.gz: d46925cf270b99f4947dbf19c5e6bb3e9c139701
 SHA512:
-  metadata.gz: 3c59039b4f65766cb8beb3b22a4f871f41f2030da5cbdf0fe130b03ea4e301a4de6babae71af07308a7c99a3a2d41eeaa584e01de1bfb19d6f787b95f97e2c46
-  data.tar.gz: ebeb9e0ae9e274b9d64c5147a875cd9e288b50079527429e815cad3f0f4fbd09406e124db058a63b7c6bddc682be787b82e1590a79a310d58f98ee34d1ea8519
+  metadata.gz: 998e44dd82eb05285330ba40a02043df0bd92688095c0a8ab85662dc3e9bca4d9de231d2683aa54307ad3a8581bb7aa95039a15f5ae0b41cb421f02ddfb40453
+  data.tar.gz: aeedac15704a869d5b86a617889bd022858f045d95008085db318ff33873c433fcf7f9e6da23587a8aa8ef704c3965312c5bcdaae48002008977d4c5da7dcd4b

data/.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,47 @@
+<!--
+Thanks for your interest in the project. I appreciate bugs filed and PRs submitted!
+Please make sure that you are familiar with and follow the Code of Conduct for
+this project (found in the CODE_OF_CONDUCT.md file).
+
+Please fill out this template with all the relevant information so we can
+understand what's going on and fix the issue.
+
+I may ask you to submit the fix (after giving some direction).
+-->
+
+Environment:
+
+<!--
+  Please provide the version of this project where the issue occurred as well as the
+  versions of other environmental factors. This could be virtual machine version, os
+  version, browser version etc.
+-->
+
+Relevant code or config:
+
+```
+
+```
+
+What you did:
+
+
+
+What happened:
+
+<!-- Please provide the full error message/screenshots/anything -->
+
+Reproduction repository:
+
+<!--
+If possible, please create a repository that reproduces the issue with the
+minimal amount of code possible. It is highly recommended you take the time
+to read "How to create a Minimal, Complete, and Verifiable example" at
+https://stackoverflow.com/help/mcve
+-->
+
+Problem description:
+
+
+
+Suggested solution:

data/.travis.yml

@@ -1,5 +1,4 @@
 language: ruby
-sudo: false
 rvm:
   - 2.3.1
 git:

data/CONTRIBUTING.md

@@ -1,19 +1,34 @@
 # How to Contribute
 
-Pull requests are greatly appreciated and are what makes opensource great. Here's a quick guide:
+We'd love to accept your patches and contributions to this project. Pull requests are part of
+what makes open source great. There are just a few small guidelines you need to follow.
 
-* Fork it
-* Create your feature branch (`git checkout -b my-new-feature`)
-* Commit your changes (`git commit -am 'Add some feature'`)
-* Push to the branch (`git push origin my-new-feature`)
-* Create new Pull Request
+## Code of Conduct
 
-Pester us if we don't get your Pull Requests merged in a timely fashion. :)
+Participation in this project comes under the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md)
+
+## Submitting code via Pull Requests
+
+- We follow the [Github Pull Request Model](https://help.github.com/articles/about-pull-requests/) for
+  all contributions.
+- For large bodies of work, we recommend creating an issue outlining the feature that you wish to build,
+  and describing how it will be implemented. This gives a chance for review to happen early, and ensures
+  no wasted effort occurs.
+- All submissions, will require review before being merged.
+- Finally - *Thanks* for considering submitting code to the project!
+
+## Formatting
+
+When submitting pull requests, make sure to do the following:
+
+- Maintain the same code style as the rest of the project.
+- Remove trailing whitespace. Many editors will do this automatically.
+- Ensure any new files have [a trailing newline](https://stackoverflow.com/questions/5813311/no-newline-at-end-of-file)
 
 ## How to speed the merging of pull requests
 
-* Describe your changes in the CHANGELOG.
-* Give yourself some credit in the appropriate place (usually the CHANGELOG).
+* Describe your changes in the CHANGELOG.md (if present).
+* Give yourself some credit in the appropriate place (usually the CHANGELOG.md).
 * Make commits of logical units.
 * Ensure your commit messages help others understand what you are doing and why.
 * Check for unnecessary whitespace with `git diff --check` before committing.
@@ -23,4 +38,6 @@ Pester us if we don't get your Pull Requests merged in a timely fashion. :)
 ## Additional Resources
 
 * [General GitHub documentation](http://help.github.com/)
-* [GitHub pull request documentation](http://help.github.com/send-pull-requests/)
+* [How to write a good Git Commit message](https://chris.beams.io/posts/git-commit/) -
+  Great way to make sure your Pull Requests get accepted.
+* [An Open Source Etiquette Guidebook](https://css-tricks.com/open-source-etiquette-guidebook/#article-header-id-1)

data/README.md

@@ -1,6 +1,6 @@
 # zapwhite
 
-[![Build Status](https://secure.travis-ci.org/realityforge/zapwhite.png?branch=master)](http://travis-ci.org/realityforge/zapwhite)
+[![Build Status](https://secure.travis-ci.org/realityforge/zapwhite.svg?branch=master)](http://travis-ci.org/realityforge/zapwhite)
 
 A simple tool to normalize whitespace in git repositories. The tool:
 

data/lib/reality/zapwhite.rb

@@ -203,6 +203,11 @@ module Reality
 
       attributes.text_rule('.node-version')
 
+      # Bazel defaults
+      attributes.text_rule('.bazelrc')
+      attributes.text_rule('BUILD')
+      attributes.text_rule('*.bzl')
+
       # Ruby defaults
       attributes.text_rule('Gemfile')
       attributes.text_rule('*.gemspec')

data/zapwhite.gemspec

@@ -2,7 +2,7 @@
 
 Gem::Specification.new do |s|
   s.name               = %q{zapwhite}
-  s.version            = '2.10.0'
+  s.version            = '2.11.0'
   s.platform           = Gem::Platform::RUBY
 
   s.authors            = ['Peter Donald']
@@ -15,10 +15,8 @@ Gem::Specification.new do |s|
   s.files              = `git ls-files`.split("\n")
   s.test_files         = `git ls-files -- {spec}/*`.split("\n")
   s.executables        = `git ls-files -- bin/*`.split("\n").map { |f| File.basename(f) }
-  s.default_executable = []
   s.require_paths      = %w(lib)
 
-  s.has_rdoc           = false
   s.rdoc_options       = %w(--line-numbers --inline-source --title zapwhite)
 
   s.add_dependency 'gitattributes', '= 2.9.0'

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: zapwhite
 version: !ruby/object:Gem::Version
-  version: 2.10.0
+  version: 2.11.0
 platform: ruby
 authors:
 - Peter Donald
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-04-25 00:00:00.000000000 Z
+date: 2019-03-05 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: gitattributes
@@ -60,6 +60,7 @@ extensions: []
 extra_rdoc_files: []
 files:
 - ".gitattributes"
+- ".github/ISSUE_TEMPLATE.md"
 - ".gitignore"
 - ".ruby-version"
 - ".travis.yml"