manageiq-style 1.0.0 → 1.0.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ccd4a109779db16869e430273f004338e16e1de877e2edf1c408229bf1d9968d
-  data.tar.gz: 91cc356ab5b92b529667939a7bb75c1861547a18056ed47f40db3c56c408793d
+  metadata.gz: 87713f5170c0b2e2264839443cd86efd7e0a2e0cf7350520c40bf3cad60a569d
+  data.tar.gz: 954625f619b519fe56af127ad53ba885e2c53b8accf191dcbd6bde88dbaca507
 SHA512:
-  metadata.gz: 578897c59ec8aa6fd48fa877e862d0241ab4961db33fc3cdff140dcedf2346b871965a2eb8f17be75a74092f3548310ab2b7b828618c48af1214db20375d8858
-  data.tar.gz: 1d2bd3c89623af4d07e6ce8d953f4dbd677bc813309dd41082b1cf3671953074af884594200f0b51d13d0d7f97efb8e8e5e9946d11538ca0685f73c73db103c0
+  metadata.gz: a4609edf44018bd8c3b0f315fbde1b8a36dceb41b19002f518a77186adaad012c1bdfa115af1c9b4ea9159eb7482700309809d04d13eada0c443e85d67b56b1c
+  data.tar.gz: 7a6712cd6fe92ec007c80990e96cecac67f39353b435c2e35514cf7c10dc2d6686a956c035d326a0455bb07f486b3bb9296a5e6362f479275df4f6a48378b480

data/.gitignore

@@ -6,6 +6,6 @@
 /pkg/
 /spec/reports/
 /tmp/
-
+Gemfile.lock
 # rspec failure tracking
 .rspec_status

data/.rubocop_base.yml

@@ -64,6 +64,8 @@ Rails/HttpStatus:
   EnforcedStyle: numeric
 Rails/ReadWriteAttribute:
   AutoCorrect: false
+Style/AccessModifierDeclarations:
+  Enabled: false
 Style/ClassAndModuleChildren:
   Enabled: false
 Style/ClassCheck:

data/README.md

@@ -37,4 +37,4 @@ Bug reports and pull requests are welcome on GitHub at https://github.com/[USERN
 
 ## Code of Conduct
 
-Everyone interacting in the Manageiq::Style project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/[USERNAME]/manageiq-style/blob/master/CODE_OF_CONDUCT.md).
+Everyone interacting in the Manageiq::Style project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/ManageIQ/.github/blob/master/CODE_OF_CONDUCT.md).

data/lib/manageiq/style/version.rb

@@ -1,5 +1,5 @@
 module Manageiq
   module Style
-    VERSION = "1.0.0"
+    VERSION = "1.0.1"
   end
 end

data/manageiq-style.gemspec

@@ -24,7 +24,6 @@ Gem::Specification.new do |spec|
   spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
   spec.require_paths = ["lib"]
 
-  spec.add_runtime_dependency "haml_lint", "~> 0.35.0"
   spec.add_runtime_dependency "rubocop",   "~> 0.82.0"
   spec.add_runtime_dependency "rubocop-performance"
   spec.add_runtime_dependency "rubocop-rails"

metadata

@@ -1,29 +1,15 @@
 --- !ruby/object:Gem::Specification
 name: manageiq-style
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.0.1
 platform: ruby
 authors:
 - Brandon Dunne
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2020-05-19 00:00:00.000000000 Z
+date: 2020-06-19 00:00:00.000000000 Z
 dependencies:
-- !ruby/object:Gem::Dependency
-  name: haml_lint
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: 0.35.0
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: 0.35.0
 - !ruby/object:Gem::Dependency
   name: rubocop
   requirement: !ruby/object:Gem::Requirement
@@ -80,7 +66,6 @@ files:
 - ".rubocop_base.yml"
 - ".rubocop_cc_base.yml"
 - ".travis.yml"
-- CODE_OF_CONDUCT.md
 - Gemfile
 - LICENSE.txt
 - README.md

data/CODE_OF_CONDUCT.md

@@ -1,74 +0,0 @@
-# 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 brandondunne@hotmail.com. 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 [https://contributor-covenant.org/version/1/4][version]
-
-[homepage]: https://contributor-covenant.org
-[version]: https://contributor-covenant.org/version/1/4/