git-conform 1.2.1 → 1.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6e6e1ebbec3350945a83b600a63dbd754a4f8ac2876336109abcd149006bd403
-  data.tar.gz: 33279101c619baee51297f9a6bb43924e48f34ad30cb339222e987ac98bf8824
+  metadata.gz: 794753b551fb257092207daf99071ae331f2ac2888e01fcb56bfd8e40893c16f
+  data.tar.gz: 5b1e6594497c33d74f1287f16641bde4baf86046f6c61b38caf417f83c6c4049
 SHA512:
-  metadata.gz: 5cbe2d0f9f0e41fbbe864bf3006a8fa69073ac54162b550d3a2c542b9d951694f180043fedb7ee07c7dd51026f361642c630059eeb816f215c7783a88f1697c2
-  data.tar.gz: 5c1f9888c15768dee527bd2006db478b75d9f559c8f719d01e5de40960a518d0dc681975efd71578e93463eb82a9482078d61d4582ce472685059c5de9ff0211
+  metadata.gz: f371865c3408b7dde5d3244446056856845601670fa3c2dfe2f0b566935137e221e6538a0de8acf7b5adc5d0a7ca4e5a4103d860b559b8cac4f6a130edd3051b
+  data.tar.gz: 58a395b20f5232ad1624fd36f41c56ebc7f2b744845c517648b0efefab727f2ef7f210aad263596c93dafca4151ecfb278e14f53818f1c0c8ca9be8aff0dccca

data/.gitconform

@@ -0,0 +1,9 @@
+[git "conform"]
+	checker = CarriageReturnCharacterChecker
+	checker = FileNotEmptyChecker
+	checker = LowercaseFilenameChecker
+	checker = NonAsciiCharacterChecker
+	checker = NonAsciiFilenameChecker
+	checker = TabCharacterChecker
+	checker = TrailingWhitespaceChecker
+	checker = WhitespaceFilenameChecker

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at peter.vandenberk@simplybusiness.co.uk. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    git-conform (1.2.1)
+    git-conform (1.3.0)
       rugged (~> 0.27)
       slop (~> 4.6)
 
@@ -52,4 +52,4 @@ DEPENDENCIES
   rubocop
 
 BUNDLED WITH
-   1.17.3
+   2.0.2

data/lib/git/conform/version.rb

@@ -1,7 +1,7 @@
 module Git
   module Conform
     NAME = 'git-conform'.freeze
-    VERSION = '1.2.1'.freeze
+    VERSION = '1.3.0'.freeze
 
     def self.version
       "#{NAME} v#{VERSION}"

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: git-conform
 version: !ruby/object:Gem::Version
-  version: 1.2.1
+  version: 1.3.0
 platform: ruby
 authors:
 - Peter Vandenberk
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2019-07-05 00:00:00.000000000 Z
+date: 2019-07-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rugged
@@ -130,10 +130,12 @@ executables:
 extensions: []
 extra_rdoc_files: []
 files:
+- ".gitconform"
 - ".gitignore"
 - ".pryrc"
 - ".rubocop.yml"
 - ".ruby-version"
+- CODE_OF_CONDUCT.md
 - Gemfile
 - Gemfile.lock
 - LICENSE.txt
@@ -180,7 +182,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.0.2
+rubygems_version: 3.0.4
 signing_key: 
 specification_version: 4
 summary: Conformity checking for git repositories