github-ripper 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: c07be0378c5d4f3bb3bc6a425abf44d04aa6c645a4365cf2ca16da9fb662f03c
+  data.tar.gz: e9ad265ec9bb24a5d2555a85fd239b8d350bcdd26c43674e55db19dcc80f32ca
+SHA512:
+  metadata.gz: 979ad3fe721c917d639c2fd60187cb4233d40b7fab5904347c41338c012e65a7a1983e6d0c722290c9746ecbc1eb84904c1f57aaeb2bbe1f674bb3304d443f00
+  data.tar.gz: d0b7a06866c014147afffca387199240185644029b8a69214c88619c816f3ca4797feb96b5999549fac91496fbf708a9b1b0266cb53140be095ac7ee179c9e16

data/.github/CODEOWNERS

@@ -0,0 +1,5 @@
+#
+# These owners will be the default owners for everything in the repo.
+#
+*	@TGWolf
+

data/.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# 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, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, 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 . 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://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

data/.github/CONTRIBUTING.md

@@ -0,0 +1,9 @@
+# Contributing
+
+Please refer to the [contributing](https://github.com/WolfSoftware/contributing) documentation.
+
+## Important
+
+ALL commits must be signed to ensure the identity of the developer, any pull requests that are made with unsigned commits will be rejected as a matter of course.
+
+> This project has a [code of conduct](CODE_OF_CONDUCT.md). By interacting with this repository, organization, or community you agree to abide by its terms.

data/.github/FUNDING.yml

@@ -0,0 +1,4 @@
+# Funding
+# https://help.github.com/en/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository
+
+ko_fi: wolfsoftware

data/.github/ISSUE_TEMPLATE/ask_question.md

@@ -0,0 +1,10 @@
+---
+name: Ask a question
+about: Feel free to ask us a question
+title: ''
+labels: 'question'
+assignees: 'TGWolf'
+
+---
+
+**What would you like to know?**

data/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,30 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: 'bug'
+assignees: 'TGWolf'
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1.
+2.
+3.
+4.
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Environment**
+Any relevant information about your environment, OS version, virtualised or not.
+
+**Additional context**
+Add any other context about the problem here.

data/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

data/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: 'enhancement'
+assignees: 'TGWolf'
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

data/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,28 @@
+Thanks for submitting a pull request! Please provide enough information so that others can review your pull request:
+
+**Summary**
+
+<!-- Summary of the PR -->
+
+This PR fixes/implements the following **bugs/features**
+
+* [ ] Bug 1
+* [ ] Feature 1
+* [ ] Breaking changes
+
+<!-- You can skip this if you're fixing a typo or adding an app to the Showcase. -->
+
+Explain the **motivation** for making this change. What existing problem does the pull request solve?
+
+<!-- Example: When "Adding a function to do X", explain why it is necessary to have a way to do X. -->
+
+**Test plan (required)**
+
+Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots help greatly.
+
+<!-- Make sure tests pass on both Travis. -->
+
+**Closing issues**
+
+<!-- Put `fixes #XXXX` in your comment to auto-close the issue that your PR fixes (if such). -->
+Fixes #

data/.github/SECURITY.md

@@ -0,0 +1,39 @@
+# Security Policies and Procedures
+
+This document outlines security procedures and general policies for this project.
+
+  * [Reporting a Bug](#reporting-a-bug)
+  * [Disclosure Policy](#disclosure-policy)
+  * [Comments on this Policy](#comments-on-this-policy)
+
+## Reporting a Bug
+
+We take **ALL** security related bugs and issues very seriously.
+
+If you think you have identified a security related issue, please [report it immediately](mailto:disclose@wolfsoftware.com) 
+and include the word "SECURITY" in the subject line. If you are not sure, don’t worry.
+Better safe than sorry – just send an email.
+
+* Please provide as much information as you can.
+* Please do not open issues related to any security concerns publicly.
+* Please do not include anyone else on the disclosure email.
+
+Report security bugs in third-party modules to the person or team maintaining
+the module.
+
+## Disclosure Policy
+
+When a security report is received, we will carry out the following steps:
+
+  * Confirm the problem and determine the affected versions.
+  * Audit code to find any potential similar problems.
+  * Prepare fixes for all releases still under maintenance. These fixes will be
+    released as fast as possible.
+
+We will endeavor to keep you informed of the progress towards a fix 
+and full announcement, and may ask for additional information or guidance.
+
+## Comments on this Policy
+
+If you have suggestions on how this process could be improved please submit a
+pull request.

data/.github/SUPPORT.md

@@ -0,0 +1,8 @@
+# Support
+
+If the documentation is not providing the information that you require then you have a couple of options:
+
+1. [Start a discussion](https://github.com/DevelopersToolbox/github-ripper/discussions).
+1. [Open an issue](https://github.com/DevelopersToolbox/github-ripper/issues), using the `Ask a question` option.
+
+> This project has a [code of conduct](CODE_OF_CONDUCT.md). By interacting with this repository, organization, or community you agree to abide by its terms.

data/.gitignore

@@ -0,0 +1,17 @@
+**/ab-results*
+
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+
+# rspec failure tracking
+.rspec_status
+
+/Gemfile.lock
+
+*.gem

data/.reek.yml

@@ -0,0 +1,6 @@
+---
+detectors:
+    TooManyStatements:
+        max_statements: 10
+    TooManyMethods:
+        max_methods: 20

data/.rubocop.yml

@@ -0,0 +1,31 @@
+AllCops:
+    NewCops: enable
+    TargetRubyVersion: 2.5
+
+Layout/HashAlignment:
+    EnforcedHashRocketStyle: table
+
+Layout/IndentationWidth:
+    Width: 4
+
+Layout/LineLength:
+    Enabled: false
+
+Naming/FileName:
+    Enabled: false
+
+Naming/RescuedExceptionsVariableName:
+    PreferredName: exception
+
+Style/FrozenStringLiteralComment:
+    Enabled: false
+
+Style/HashSyntax:
+    EnforcedStyle: hash_rockets
+
+Style/RaiseArgs:
+    EnforcedStyle: compact
+
+Style/WordArray:
+    Enabled: false
+

data/.travis.yml

@@ -0,0 +1,129 @@
+matrix:
+  include:
+  - language: ruby
+    name: Bundler (rvm 2.5)
+    rvm: 2.5
+    before_install:
+    - gem install bundler
+  - language: ruby
+    name: Bundler (rvm 2.6)
+    rvm: 2.6
+    before_install:
+    - gem install bundler
+  - language: ruby
+    name: Bundler (rvm 2.7)
+    rvm: 2.7
+    before_install:
+    - gem install bundler
+  - language: ruby
+    name: Bundler (rvm 3.0)
+    rvm: 3.0
+    before_install:
+    - gem install bundler
+  - language: ruby
+    name: Rubocop (rvm 2.5)
+    rvm: 2.5
+    before_install:
+    - git clone https://github.com/TravisToolbox/rubocop.git
+    install:
+    - "./rubocop/install.sh"
+    script:
+    - "./rubocop/scan.sh"
+  - language: ruby
+    name: Rubocop (rvm 2.6)
+    rvm: 2.6
+    before_install:
+    - git clone https://github.com/TravisToolbox/rubocop.git
+    install:
+    - "./rubocop/install.sh"
+    script:
+    - "./rubocop/scan.sh"
+  - language: ruby
+    name: Rubocop (rvm 2.7)
+    rvm: 2.7
+    before_install:
+    - git clone https://github.com/TravisToolbox/rubocop.git
+    install:
+    - "./rubocop/install.sh"
+    script:
+    - "./rubocop/scan.sh"
+  - language: ruby
+    name: Rubocop (rvm 3.0)
+    rvm: 3.0
+    before_install:
+    - git clone https://github.com/TravisToolbox/rubocop.git
+    install:
+    - "./rubocop/install.sh"
+    script:
+    - "./rubocop/scan.sh"
+  - language: ruby
+    name: Reek (rvm 2.5)
+    rvm: 2.5
+    before_install:
+    - git clone https://github.com/TravisToolbox/reek.git
+    install:
+    - "./reek/install.sh"
+    script:
+    - "./reek/scan.sh"
+  - language: ruby
+    name: Reek (rvm 2.6)
+    rvm: 2.6
+    before_install:
+    - git clone https://github.com/TravisToolbox/reek.git
+    install:
+    - "./reek/install.sh"
+    script:
+    - "./reek/scan.sh"
+  - language: ruby
+    name: Reek (rvm 2.7)
+    rvm: 2.7
+    before_install:
+    - git clone https://github.com/TravisToolbox/reek.git
+    install:
+    - "./reek/install.sh"
+    script:
+    - "./reek/scan.sh"
+  - language: ruby
+    name: Reek (rvm 3.0)
+    rvm: 3.0
+    before_install:
+    - git clone https://github.com/TravisToolbox/reek.git
+    install:
+    - "./reek/install.sh"
+    script:
+    - "./reek/scan.sh"
+  - language: ruby
+    name: YAML Linting (rvm 2.7)
+    rvm: 2.7
+    before_install:
+    - git clone https://github.com/TravisToolbox/yaml-lint
+    install:
+    - "./yaml-lint/install.sh"
+    script:
+    - "./yaml-lint/scan.sh"
+  - language: bash
+    name: Shellcheck (Bash)
+    os: linux
+    arch: arm64-graviton2
+    before_install:
+    - git clone https://github.com/TravisToolbox/shellcheck
+    install:
+    - "./shellcheck/install.sh"
+    script:
+    - "./shellcheck/scan.sh"
+  - language: ruby
+    name: Link Checking (rvm 2.7)
+    rvm: 2.7
+    env:
+    - WHITELIST="https://img.shields.io"
+    - EXCLUDE_FILES="CHANGELOG.md,github-lister-core.gemspec"
+    before_install:
+    - git clone https://github.com/TravisToolbox/awesomebot
+    install:
+    - "./awesomebot/install.sh"
+    script:
+    - "./awesomebot/scan.sh"
+notifications:
+  email: false
+  slack:
+    secure: SUarMpNZePsGIzmwZq/jCnEa8nKPE31tnsYF7PjihOQNuMjRjQps+fuVqBCm7tyxf+J79mQ7CelID3zwRN8jWP7pF1ZDJEi6tgLfIj6cCW3UlmKdn3+wzilrjxL32nkjaJvpgh+5Sv5y8PaWg2x82Utp97fh4D/x1d2PcYLjKx8g3iC5FxjDxkydC65ERaEZpTCyFskG2obnJBXUCNdO1b+7jJUxIhuPTkdc/wt51mgpEo+iz3GY4aMSBTOA1Ug5lV3vb8ZUS8YrUdC62/nIEToRzO/TqNt/Pyhzpbj3TDAXlmmw/Cvlsbe4ip670d7MLLxUv7Dyb1zB0+UZiHmLo5eivg2OaYKcjqXIQUPSdfh8cDyjVL1+67Qzeoe8QH1NwZ1kncu38aBmHUQSZgekBbE1yF9PxaQWJFxRWt6dkIBBEWUfSVKBZ8f74vJuZjpJQm95OvFxNbqK71yJER9vTfDuUmCOi1+dwYRYeXF0T0S7zju8LQy0EW1rf7QGSFMWVFASMy7i8oJBESQEAAA5ohWPcGeg7mSeEirLPnstyJeNdULXdFYx6YqrCW+DNsDM67SCPRmLseb8bxwFTPQOMi3vtLFDIp5PoGrRbha4YYYJBwO3QCO6XPHRcIe/wNfDC58uc71l2yYkIY4dT119wzqDxznDRiOEgztnwaY/lHw=