Currently there's no test coverage on CLI. This adds tests for a new class Parser which will replace the command line options currently in bin/annotate.

The technical direction I'm planning to go is to remove ENV variables completely and to have things passed into as arguments. Will be adding deprecation warnings in 3.0 and then deprecate ENV variables completely in 3.1. Deprecation warnings will be non-blocking in 3.0 when an ENV variable is set and an argument isn't passed in, and will becoming blocking in 3.1.

`BigDecimal.new` is deprecated in future version of Ruby in favor of using `BigDecimal(...)`.

* Update rubocop requirement from ~> 0.67.2 to ~> 0.68.1

Updates the requirements on [rubocop](https://github.com/rubocop-hq/rubocop) to permit the latest version.
- [Release notes](https://github.com/rubocop-hq/rubocop/releases)
- [Changelog](https://github.com/rubocop-hq/rubocop/blob/master/CHANGELOG.md)
- [Commits](https://github.com/rubocop-hq/rubocop/compare/v0.67.2...v0.68.1)

* Rerun rubocop --auto-gen-config

The cop Layout/IndexHash was renamed to Layout/IndentFirstHashElement
causing CI to fail. By rerunning the config generator this updates the
correct cop name so that Rubocop no longer fails in CI.

* Update Ruby 2.2.7 to 2.2.10

There are 3 patch versions of security and vulnerability fixes and 2.2.7
was released back in March 28 2017.

* Use older version of RubyGems for Ruby 2.2

The current build tries to update to RubyGems 3. This currently fails
for Ruby 2.2 because RubyGems 3.0.0 drops support for Ruby 2.2.X.

This change should support Ruby 2.2 by explicitly installing RubyGems
2.7 after failing to find a compatible version of 3.

Handle potential negative padding in `#mb_chars_ljust` when having a `col_length` > 16, the default hardcoded value of `bare_type_allowance`.

Travis was trying to publish gem multiple times in the matrix builds.  This should restrict the gem publish to a single build.

In AnnotateRoutes, there were many public methods that is not used in other classes or modules.

Before my extension, I made these methods private and sort them in order of appearance.

All tests were passed.

Please trace each commits carefully. I didn't nothing special. The commits consist of coordinating code.

Updates the requirements on [ruby_dep](https://github.com/e2/ruby_dep) to permit the latest version.
- [Release notes](https://github.com/e2/ruby_dep/releases)
- [Commits](https://github.com/e2/ruby_dep/compare/v1.3.1...v1.5.0)
Signed-off-by: dependabot[bot] <support@dependabot.com>

* Update rubocop requirement from ~> 0.46.0 to ~> 0.67.2

Updates the requirements on [rubocop](https://github.com/rubocop-hq/rubocop) to permit the latest version.
- [Release notes](https://github.com/rubocop-hq/rubocop/releases)
- [Changelog](https://github.com/rubocop-hq/rubocop/blob/master/CHANGELOG.md)
- [Commits](https://github.com/rubocop-hq/rubocop/compare/v0.46.0...v0.67.2)
Signed-off-by: dependabot[bot] <support@dependabot.com>

* Make changes to let Rubocop pass in CI

Add --frozen option to abort instead of write annotation.
This is mainly for CI environment to detect missing annotation.
Similar motivation with bundle install --frozen.

works like:
```
$ rake db:migrate frozen=yes

annotate error. spec/models/user_spec.rb needs to be updated, but annotate was run with `--frozen
```

* Update rubocop requirement from ~> 0.46.0 to ~> 0.65.0

Updates the requirements on [rubocop](https://github.com/rubocop-hq/rubocop) to permit the latest version.
- [Release notes](https://github.com/rubocop-hq/rubocop/releases)
- [Changelog](https://github.com/rubocop-hq/rubocop/blob/master/CHANGELOG.md)
- [Commits](https://github.com/rubocop-hq/rubocop/compare/v0.46.0...v0.65.0)
Signed-off-by: dependabot[bot] <support@dependabot.com>

* Regenerate .rubocop_todo.yml

Since Rails full engines run as non-namespaced applications but all their app-related tasks still prefixed with `app:`

- Use Rake::Task#enhance insteaad of defining same tasks again
- Remove hooking db:migrate:change task which doesn't exist
- Fix hooking db:migrate:reset task so that the annotation runs after
  all migration tasks (#548)

This fixes alignment of Japanese, Korean and Chinese fullwidth character comments.

The displayed widths of multi-byte fullwidth characters are generally
twice as large as the ASCII characters, but String#size returns only the number of characters.
So if the column comment contains fullwidth multibyte characters, the alignment is broken.

* refactor and simplify returns for annotate_one_file
* fix rubocop offenses

In rails 4, columns do not respond to `bigint?`.  However, in both rails
4 and rails 5, columns do respond to `sql_type`. This way, annotations
should work in both versions.

* :with_comment option is flag
* It should use `true?` instead of `fallback`.

https://github.com/thoughtbot/factory_bot/blob/master/NAME.md