doorkeeper 5.4.0.rc1 → 5.4.0.rc2

data/Appraisals

@@ -1,26 +0,0 @@
-# frozen_string_literal: true
-
-appraise "rails-5-0" do
-  gem "rails", "~> 5.0.0"
-  gem "sqlite3", "~> 1.3", "< 1.4", platform: %i[ruby mswin mingw x64_mingw]
-end
-
-appraise "rails-5-1" do
-  gem "rails", "~> 5.1.0"
-  gem "sqlite3", "~> 1.3", "< 1.4", platform: %i[ruby mswin mingw x64_mingw]
-end
-
-appraise "rails-5-2" do
-  gem "rails", "~> 5.2.0"
-  gem "sqlite3", "~> 1.3", "< 1.4", platform: %i[ruby mswin mingw x64_mingw]
-end
-
-appraise "rails-6-0" do
-  gem "rails", "~> 6.0.0"
-  gem "sqlite3", "~> 1.4", platform: %i[ruby mswin mingw x64_mingw]
-end
-
-appraise "rails-master" do
-  gem "rails", git: "https://github.com/rails/rails"
-  gem "sqlite3", "~> 1.4", platform: %i[ruby mswin mingw x64_mingw]
-end

data/CODE_OF_CONDUCT.md

@@ -1,46 +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 members or current maintainer email, specified in gemspec. The project team will review and investigate all complaints, and will respond in a way that it deems 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/CONTRIBUTING.md

@@ -1,49 +0,0 @@
-# Contributing
-
-We love pull requests from everyone. By participating in this project, you agree
-to abide by the [code of conduct](CODE_OF_CONDUCT.md).
-
-Fork, then clone the repo:
-
-    git clone git@github.com:your-username/doorkeeper.git
-
-### Docker Setup
-
-Build the container image with: `docker build --pull -t doorkeeper:test .`
-Run the tests with: `docker run -it --rm doorkeeper:test`
-
-### Local Setup
-
-Set up Ruby dependencies via Bundler
-
-    bundle install
-
-Make sure the tests pass:
-
-    rake
-
-Make your change.
-Write tests.
-Follow our [style guide](.rubocop.yml).
-Make the tests pass:
-
-    rake
-
-Add notes on your change to the `CHANGELOG.md` file.
-
-Write a [good commit message][commit].
-Push to your fork.
-[Submit a pull request][pr].
-
-[commit]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
-[pr]: https://github.com/doorkeeper-gem/doorkeeper/compare/
-
-If [Hound] catches style violations, fix them.
-
-[hound]: https://houndci.com
-
-Wait for us.
-We try to at least comment on pull requests within one business day.
-We may suggest changes.
-
-Thank you for your contribution!

data/Dangerfile

@@ -1,67 +0,0 @@
-CHANGELOG_FILE = "CHANGELOG.md"
-GITHUB_REPO = "https://github.com/doorkeeper-gem/doorkeeper"
-
-def changelog_changed?
-  git.modified_files.include?(CHANGELOG_FILE) || git.added_files.include?(CHANGELOG_FILE)
-end
-
-def changelog_entry_example
-  pr_number = github.pr_json["number"]
-  pr_title = github.pr_title
-                   .sub(/[?.!,;]?$/, "")
-                   .capitalize
-
-  "- [##{pr_number}] #{pr_title}."
-end
-
-# --------------------------------------------------------------------------------------------------------------------
-# Has any changes happened inside the actual library code?
-# --------------------------------------------------------------------------------------------------------------------
-has_app_changes = !git.modified_files.grep(/lib|app/).empty?
-has_spec_changes = !git.modified_files.grep(/spec/).empty?
-
-# --------------------------------------------------------------------------------------------------------------------
-# You've made changes to lib, but didn't write any tests?
-# --------------------------------------------------------------------------------------------------------------------
-if has_app_changes && !has_spec_changes
-  warn("There're library changes, but not tests. That's OK as long as you're refactoring existing code.", sticky: false)
-end
-
-# --------------------------------------------------------------------------------------------------------------------
-# You've made changes to specs, but no library code has changed?
-# --------------------------------------------------------------------------------------------------------------------
-if !has_app_changes && has_spec_changes
-  message("We really appreciate pull requests that demonstrate issues, even without a fix. That said, the next step is to try and fix the failing tests!", sticky: false)
-end
-
-# Mainly to encourage writing up some reasoning about the PR, rather than
-# just leaving a title
-if github.pr_body.length < 10
-  fail "Please provide a summary in the Pull Request description"
-end
-
-# --------------------------------------------------------------------------------------------------------------------
-# Have you updated CHANGELOG.md?
-# --------------------------------------------------------------------------------------------------------------------
-# Add a CHANGELOG entry for app changes
-if has_app_changes && !changelog_changed?
-  markdown <<-MARKDOWN
-Here's an example of a #{CHANGELOG_FILE} entry:
-```markdown
-#{changelog_entry_example}
-```
-  MARKDOWN
-
-  warn(
-    "Please include a changelog entry. \nYou can find it at [#{CHANGELOG_FILE}](#{GITHUB_REPO}/blob/master/#{CHANGELOG_FILE})." +
-      "You can skip this warning only if you made some typo fix or other small changes that didn't affect the API."
-  )
-end
-
-if git.commits.any? { |commit| commit.message =~ /^Merge branch '#{github.branch_for_base}'/ }
-  warn("Please rebase to get rid of the merge commits in this PR")
-end
-
-if git.commits.length > 1
-  warn("Please squash all your commits to a single one")
-end

data/Dockerfile

@@ -1,29 +0,0 @@
-FROM ruby:2.6.5-alpine
-
-RUN apk add --no-cache \
-  ca-certificates \
-  wget \
-  openssl \ 
-  bash \
-  build-base \
-  git \
-  sqlite-dev \
-  tzdata
-
-ENV LANG en_US.UTF-8
-ENV LANGUAGE en_US:en
-ENV LC_ALL en_US.UTF-8
-
-ENV BUNDLER_VERSION 2.1.4
-RUN gem install bundler -v ${BUNDLER_VERSION} -i /usr/local/lib/ruby/gems/$(ls /usr/local/lib/ruby/gems) --force
-
-WORKDIR /srv
-
-COPY Gemfile doorkeeper.gemspec /srv/
-COPY lib/doorkeeper/version.rb /srv/lib/doorkeeper/version.rb
-
-RUN bundle install
-
-COPY . /srv/
-
-CMD ["rake"]

data/Gemfile

@@ -1,25 +0,0 @@
-# frozen_string_literal: true
-
-source "https://rubygems.org"
-git_source(:github) { |repo| "https://github.com/#{repo}.git" }
-
-gemspec
-
-gem "rails", "~> 6.0"
-
-gem "rspec-core"
-gem "rspec-expectations"
-gem "rspec-mocks"
-gem "rspec-rails", "~> 4.0"
-gem "rspec-support"
-
-gem "rubocop", "~> 0.80"
-gem "rubocop-performance", require: false
-gem "rubocop-rails", require: false
-
-gem "bcrypt", "~> 3.1", require: false
-
-gem "activerecord-jdbcsqlite3-adapter", platform: :jruby
-gem "sqlite3", "~> 1.4", platform: %i[ruby mswin mingw x64_mingw]
-
-gem "tzinfo-data", platforms: %i[mingw mswin x64_mingw]

data/NEWS.md

@@ -1 +0,0 @@
-Document moved [here](CHANGELOG.md)

data/RELEASING.md

@@ -1,11 +0,0 @@
-# Releasing Doorkeeper
-
-How to release Doorkeeper in five easy steps!
-
-1. Update `lib/doorkeeper/version.rb` file accordingly.
-2. Update `CHANGELOG.md` to reflect the changes since last release.
-3. Commit changes: `git commit -am 'Bump to vVERSION'`.
-4. Build and publish the gem.
-4. Create GitHub release.
-5. Announce the new release, making sure to say “thank you” to the contributors
-   who helped shape this version!

data/Rakefile

@@ -1,28 +0,0 @@
-# frozen_string_literal: true
-
-require "bundler/setup"
-require "rspec/core/rake_task"
-
-desc "Default: run specs."
-task default: :spec
-
-desc "Run all specs"
-RSpec::Core::RakeTask.new(:spec) do |config|
-  config.verbose = false
-end
-
-namespace :doorkeeper do
-  desc "Install doorkeeper in dummy app"
-  task :install do
-    cd "spec/dummy"
-    system "bundle exec rails g doorkeeper:install --force"
-  end
-
-  desc "Runs local test server"
-  task :server do
-    cd "spec/dummy"
-    system "bundle exec rails server"
-  end
-end
-
-Bundler::GemHelper.install_tasks

data/SECURITY.md

@@ -1,15 +0,0 @@
-# Reporting security issues in Doorkeeper
-
-Hello! Thank you for wanting to disclose a possible security
-vulnerability within the Doorkeeper gem! Please follow our disclosure
-policy as outlined below:
-
-1. Do NOT open up a GitHub issue with your report. Security reports
-   should be kept private until a possible fix is determined.
-2. Send an email to Nikita Bulai at bulaj.nikita AT gmail.com or one of
-   the others Doorkeeper maintainers listed in gemspec. You should receive
-   a prompt response.
-3. Be patient. Since Doorkeeper is in a stable maintenance phase, we want to
-   do as little as possible to rock the boat of the project.
-
-Thank you very much for adhering for these policies!

data/UPGRADE.md

@@ -1,2 +0,0 @@
-See [Upgrade Guides](https://github.com/doorkeeper-gem/doorkeeper/wiki/Migration-from-old-versions)
-in the project Wiki.

data/bin/console

@@ -1,30 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-require "bundler/setup"
-require "rails/all"
-require "doorkeeper"
-
-# You can add fixtures and/or initialization code here to make experimenting
-# with your gem easier. You can also use a different console, if you like.
-
-# (If you use this, don't forget to add pry to your Gemfile!)
-# require "pry"
-# Pry.start
-
-# Default Doorkeeper config
-Doorkeeper.configure do
-  orm :active_record
-end
-
-# Generate in-memory database for testing
-ActiveRecord::Base.establish_connection(
-  adapter: "sqlite3",
-  database: ":memory:",
-)
-
-# Load database schema
-load File.expand_path("../spec/dummy/db/schema.rb", __dir__)
-
-require "irb"
-IRB.start(__FILE__)

data/doorkeeper.gemspec

@@ -1,42 +0,0 @@
-# frozen_string_literal: true
-
-$LOAD_PATH.unshift File.expand_path("lib", __dir__)
-
-require "doorkeeper/version"
-
-Gem::Specification.new do |gem|
-  gem.name        = "doorkeeper"
-  gem.version     = Doorkeeper.gem_version
-  gem.authors     = ["Felipe Elias Philipp", "Tute Costa", "Jon Moss", "Nikita Bulai"]
-  gem.email       = %w[bulaj.nikita@gmail.com]
-  gem.homepage    = "https://github.com/doorkeeper-gem/doorkeeper"
-  gem.summary     = "OAuth 2 provider for Rails and Grape"
-  gem.description = "Doorkeeper is an OAuth 2 provider for Rails and Grape."
-  gem.license     = "MIT"
-
-  gem.files         = `git ls-files`.split("\n").reject { |file| file.start_with?(".") }
-  gem.test_files    = `git ls-files -- spec/*`.split("\n")
-  gem.require_paths = ["lib"]
-
-  gem.metadata = {
-    "homepage_uri" => "https://github.com/doorkeeper-gem/doorkeeper",
-    "changelog_uri" => "https://github.com/doorkeeper-gem/doorkeeper/blob/master/CHANGELOG.md",
-    "source_code_uri" => "https://github.com/doorkeeper-gem/doorkeeper",
-    "bug_tracker_uri" => "https://github.com/doorkeeper-gem/doorkeeper/issues",
-    "documentation_uri" => "https://doorkeeper.gitbook.io/guides/",
-  }
-
-  gem.add_dependency "railties", ">= 5"
-  gem.required_ruby_version = ">= 2.4"
-
-  gem.add_development_dependency "appraisal"
-  gem.add_development_dependency "capybara"
-  gem.add_development_dependency "coveralls"
-  gem.add_development_dependency "danger", "~> 6.0"
-  gem.add_development_dependency "database_cleaner", "~> 1.6"
-  gem.add_development_dependency "factory_bot", "~> 5.0"
-  gem.add_development_dependency "generator_spec", "~> 0.9.3"
-  gem.add_development_dependency "grape"
-  gem.add_development_dependency "rake", ">= 11.3.0"
-  gem.add_development_dependency "rspec-rails"
-end

data/gemfiles/rails_5_0.gemfile

@@ -1,19 +0,0 @@
-# This file was generated by Appraisal
-
-source "https://rubygems.org"
-
-gem "rails", "~> 5.0.0"
-gem "rspec-core"
-gem "rspec-expectations"
-gem "rspec-mocks"
-gem "rspec-rails", "~> 4.0"
-gem "rspec-support"
-gem "rubocop", "~> 0.80"
-gem "rubocop-performance", require: false
-gem "rubocop-rails", require: false
-gem "bcrypt", "~> 3.1", require: false
-gem "activerecord-jdbcsqlite3-adapter", platform: :jruby
-gem "sqlite3", "~> 1.3", "< 1.4", platform: [:ruby, :mswin, :mingw, :x64_mingw]
-gem "tzinfo-data", platforms: [:mingw, :mswin, :x64_mingw]
-
-gemspec path: "../"

data/gemfiles/rails_5_1.gemfile

@@ -1,19 +0,0 @@
-# This file was generated by Appraisal
-
-source "https://rubygems.org"
-
-gem "rails", "~> 5.1.0"
-gem "rspec-core"
-gem "rspec-expectations"
-gem "rspec-mocks"
-gem "rspec-rails", "~> 4.0"
-gem "rspec-support"
-gem "rubocop", "~> 0.80"
-gem "rubocop-performance", require: false
-gem "rubocop-rails", require: false
-gem "bcrypt", "~> 3.1", require: false
-gem "activerecord-jdbcsqlite3-adapter", platform: :jruby
-gem "sqlite3", "~> 1.3", "< 1.4", platform: [:ruby, :mswin, :mingw, :x64_mingw]
-gem "tzinfo-data", platforms: [:mingw, :mswin, :x64_mingw]
-
-gemspec path: "../"

data/gemfiles/rails_5_2.gemfile

@@ -1,19 +0,0 @@
-# This file was generated by Appraisal
-
-source "https://rubygems.org"
-
-gem "rails", "~> 5.2.0"
-gem "rspec-core"
-gem "rspec-expectations"
-gem "rspec-mocks"
-gem "rspec-rails", "~> 4.0"
-gem "rspec-support"
-gem "rubocop", "~> 0.80"
-gem "rubocop-performance", require: false
-gem "rubocop-rails", require: false
-gem "bcrypt", "~> 3.1", require: false
-gem "activerecord-jdbcsqlite3-adapter", platform: :jruby
-gem "sqlite3", "~> 1.3", "< 1.4", platform: [:ruby, :mswin, :mingw, :x64_mingw]
-gem "tzinfo-data", platforms: [:mingw, :mswin, :x64_mingw]
-
-gemspec path: "../"