Initialize dependabot-bundler-parser-3.2.1.1

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,44 @@
+<!-- Thank you for contributing! -->
+### Please confirm this pull request meets the following requirements:
+
+- [ ] I followed the contributing guidelines: <https://github.com/github/explore/blob/master/CONTRIBUTING.md>.
+- [ ] I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee).
+
+### Which change are you proposing?
+
+  - [ ] Suggesting edits to an existing topic or collection
+  - [ ] Curating a new topic or collection
+  - [ ] Something that does not neatly fit into the binary options above
+
+---
+
+<!-- ⚠️ Please select either this section... ⚠️ -->
+### Editing an existing topic or collection
+
+I'm suggesting these edits to an existing topic or collection:
+- [ ] Image (and my file is `*.png`, square, dimensions 288x288, size <= 75 kB)
+- [ ] Content (and my changes are in `index.md`)
+
+> Please replace this line with an explanation of why you think these changes should be made.
+
+<!-- ⚠️ ... or this section ⚠️ -->
+### Curating a new topic or collection
+
+- [ ] I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. `https://github.com/topics/[NAME]` or `https://github.com/collections/[NAME]`)
+- [ ] My folder contains a `*.png` image (if applicable) and `index.md`
+- [ ] All required fields in my `index.md` conform to the Style Guide and API docs: <https://github.com/github/explore/tree/master/docs>
+
+> Please replace this line with an explanation of why you think this topic or collection should be curated.
+
+<!-- ⚠️ ... or this section ⚠️ -->
+### Something that does not neatly fit into the binary options above
+
+- [ ] My suggested edits are not about an existing topic or collection, or at least not a single one
+- [ ] My suggested edits are not about curating a new topic or collection, or at least not a single one
+- [ ] My suggested edits conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs
+
+> Please replace this line with an explanation of your proposed changes.
+
+---
+
+**Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.**

.github/dependabot.yml

@@ -0,0 +1,15 @@
+version: 2
+updates:
+- package-ecosystem: bundler
+  directory: "/"
+  schedule:
+    interval: daily
+    time: "10:00"
+    timezone: Europe/Vienna
+  pull-request-branch-name:
+    separator: "-"
+  open-pull-requests-limit: 99
+  allow:
+  - dependency-type: direct
+  - dependency-type: indirect
+  rebase-strategy: disabled

.github/workflows/pull_request.yml

@@ -0,0 +1,33 @@
+name: CI/Rubocop
+
+on: [push, pull_request]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v2
+    - name: Setup Ruby
+      uses: actions/setup-ruby@v1
+      with:
+        ruby-version: 2.7
+    - name: Install bundler
+      run: |
+        gem install bundler:2.1.4
+        bundle config path vendor/bundle
+    - name: Cache gems
+      uses: actions/cache@v1
+      with:
+        path: vendor/bundle
+        key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile.lock') }}
+        restore-keys: |
+          ${{ runner.os }}-gems-
+    - name: Install gems
+      if: steps.cache.outputs.cache-hit != 'true'
+      run: bundle install --jobs 4 --retry 3
+    - name: Build and test with Rake/Rubocop
+      env:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      run: |
+        bundle exec rake
+        bundle exec rubocop --display-cop-names

.github/workflows/stale.yml

@@ -0,0 +1,22 @@
+name: Mark stale PRs
+on:
+  workflow_dispatch:
+  schedule:
+  - cron: "0 12 * * *"
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/stale@v3
+      with:
+        stale-pr-message: >
+          This pull request has been automatically marked as stale because it has not
+          had recent activity. It will be closed if no further activity occurs.
+          Thank you for your contributions.
+        stale-pr-label: "stale"
+        exempt-pr-labels: "pinned,security,dependencies"
+        days-before-pr-stale: 30
+        days-before-pr-close: 7
+        ascending: true
+        operations-per-run: 100

.gitignore

@@ -0,0 +1,2 @@
+.DS_Store
+scripts/

.rubocop.yml

@@ -0,0 +1,34 @@
+require: rubocop-performance
+
+AllCops:
+  TargetRubyVersion: 2.7
+  Exclude:
+    - '**/bin/**/*'
+    - '**/db/**/*'
+    - '**/script/setup'
+    - '**/vendor/**/*'
+
+Lint/AssignmentInCondition:
+  Enabled: false
+
+Metrics/BlockLength:
+  Enabled: false
+
+Layout/LineLength:
+  Max: 100
+  IgnoredPatterns: ['\A\s*#']
+
+Naming/RescuedExceptionsVariableName:
+  PreferredName: "error"
+
+Style/FrozenStringLiteralComment:
+  Enabled: false
+
+Style/StringLiterals:
+  EnforcedStyle: double_quotes
+
+Style/TrailingCommaInArrayLiteral:
+  EnforcedStyleForMultiline: consistent_comma
+
+Style/TrailingCommaInHashLiteral:
+  EnforcedStyleForMultiline: consistent_comma

.ruby-version

@@ -0,0 +1 @@
+2.7.2

Brewfile

@@ -0,0 +1,4 @@
+tap "github/bootstrap"
+
+brew "rbenv"
+brew "ruby-build"

CODEOWNERS

@@ -0,0 +1,2 @@
+*  @github/communities-oss-reviewers
+collections/made-in-india/ @github/india-community-reviewers

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# 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 to [[email protected]](mailto:[email protected]). 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/

CONTRIBUTING.md

@@ -0,0 +1,113 @@
+# Contributing
+
+Hi there! We're excited you've got ideas to improve topics and collections. You're helping the community discover valuable information.
+
+This project adheres to the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code.
+
+There are a few ways you can contribute:
+
+- Improving an existing topic or collection
+- Curating a new topic or collection
+
+As you write content, check out the [Style Guide](./docs/styleguide.md) to learn what each field means, and how it should be formatted. Following the style guide will increase the chances of your contribution being accepted.
+
+Notes: 
+  - Updates won't immediately appear once we've merged your PR. We pull in these changes regularly to GitHub.
+  - Please limit your pull request to the creation/updating of one topic or collection at a time.
+
+## Improving an existing topic or collection
+
+If a topic or collection already exists, it will be listed in its respective directory:
+
+- [topics/](https://github.com/github/explore/tree/master/topics)
+- [collections/](https://github.com/github/explore/tree/master/collections)
+
+The topic or collection name should match its URL, e.g. `https://github.com/topics/rails` corresponds to the [`topics/rails` directory](https://github.com/github/explore/tree/master/topics/rails).
+
+To make an improvement, please **open a pull request** with your proposed changes:
+
+### Update the image
+
+To update the image, simply replace the image inside the directory for the topic or collection.
+
+### Update text and links
+
+To update text and links, edit the `index.md` inside the topic or collection's directory. These files are formatted using a combination of [Front Matter](https://jekyllrb.com/docs/frontmatter/) and simple body content.
+
+For **topics**, you'll notice that, in examples like the topic "[algorithm](https://raw.githubusercontent.com/github/explore/master/topics/algorithm/index.md)," data like its canonical URL, Wikipedia URL, or display name are called out in key-value pairs, while its detailed description is accounted for in the body of the document.
+
+_/topics/algorithm/index.md_:
+```
+---
+aliases: algorithms
+display_name: Algorithm
+short_description: Algorithms are self-contained sequences that carry out a variety of tasks.
+topic: algorithm
+wikipedia_url: https://en.wikipedia.org/wiki/Algorithm
+---
+Algorithms are detailed sets of guidelines created for a computer program to complete tasks efficiently and thoroughly.
+```
+
+---
+
+Similarly, **collections** like "[music](https://raw.githubusercontent.com/github/explore/master/collections/music/index.md)" call out things like their author and display name in Front Matter variables -- with a detailed description in the body of the document. Most importantly, though, collections identify their individual collection items in [a YAML list](https://en.wikipedia.org/wiki/YAML#Basic_components) for the key "items."
+
+_/collections/music/index.md_:
+
+```
+---
+items:
+ - beetbox/beets
+ - scottschiller/SoundManager2
+ - CreateJS/SoundJS
+ - musescore/MuseScore
+ - tomahawk-player/tomahawk
+ - cashmusic/platform
+ - mopidy/mopidy
+ - AudioKit/AudioKit
+ - Soundnode/soundnode-app
+ - gillesdemey/Cumulus
+ - metabrainz/picard
+ - overtone/overtone
+ - samaaron/sonic-pi
+display_name: Music
+created_by: jonrohan
+---
+Drop the code bass with these musically themed repositories.
+```
+
+---
+
+The [pull request template](./.github/PULL_REQUEST_TEMPLATE.md) also provides guidance on the information you need to include.
+
+**Please fill out the pull request template completely.** If you do not fill out the template, your PR will be closed.
+
+## Curating a new topic or collection
+
+If a topic or collection is not yet curated, it will NOT be listed in its respective directory.
+
+We are likely to consider suggestions to curate a topic or collection that is valuable to GitHub's community. Valuable topics, for example, include those that are already [widely used by repositories](https://help.github.com/articles/classifying-your-repository-with-topics/) and could benefit from the addition of important information. When suggesting content, please consider how to make your contribution broadly useful and relevant to others, rather than serving a specific use case.
+
+Please note that all suggestions must adhere to GitHub's [Community Guidelines](https://help.github.com/articles/github-community-guidelines/) and [Terms of Service](https://help.github.com/articles/github-terms-of-service/). Per our Terms of Service, [you are responsible](https://help.github.com/articles/github-terms-of-service/#d-user-generated-content) for the content you contribute, and you must have the rights to use it.
+
+To propose a new topic or collection, please **open a pull request** with your proposed additions. The [API docs](./docs/API.md) and [style guide](./docs/styleguide.md) provide guidance on the information you need to include and how it should be formatted.
+
+This repository includes [a list of the most-used GitHub topics that don't yet have extra context](topics-todo.md). If your pull request adds one of these topics, please update topics-todo.md so that the topic is checked (marked complete).
+
+**Please fill out the pull request template completely.** If you do not fill out the template, your pull request will be closed.
+
+## Guidelines
+
+* Avoid conflicts of interest. Maintainers of a project cannot add a topic or collection for their own project. If a topic is popular enough to warrant inclusion, someone else will add or improve it.
+
+## Running tests
+
+There are some lint tests in place to ensure each topic is formatted in the way we expect. Travis
+CI will run the tests automatically. If you want to run the tests yourself locally, you will need
+Ruby and Bundler installed.
+
+You can run the tests using:
+
+```bash
+script/cibuild
+```

Gemfile

@@ -0,0 +1,12 @@
+source "https://rubygems.org"
+
+group :test do
+  gem "fastimage"
+  gem "minitest"
+  gem "octokit", "~> 6.0"
+  gem "pry", require: false
+  gem "rake"
+  gem "rubocop"
+  gem "rubocop-performance"
+  gem "safe_yaml"
+end