| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
In an executable script, the shebang line should be the first line (the
file needs to start with the bytes 0x23 0x21). Putting a comment above
it will break the script.
(Regression test included per @deivid-rodriguez)
https://github.com/rubygems/rubygems/commit/962e669feb
|
|
|
|
| |
s/overriden/overridden/
|
|
|
|
|
|
|
|
|
|
|
|
| |
The newly added specs needs to be tagged as
:readline, otherwise they fail on Windows with
the backtrace: `ZeroDivisionError: divided by 0`.
Such issues are already being skipped on Windows.
Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>
https://github.com/rubygems/rubygems/commit/391f860af4
|
|
|
|
|
|
|
|
|
|
|
| |
Since this PR was made because we missed checking
RuboCop offenses with different flags, therefore
adding tests so that all flag combinations are
tested.
Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>
https://github.com/rubygems/rubygems/commit/d08250efc2
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Gemfile wasn't properly put in the last commit.
As a result, Layout/EmptyLines inspected an offense
in the Gemfile.
This also fixes the spec w.r.t change in the task
default.
Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>
https://github.com/rubygems/rubygems/commit/d1418fddd3
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/27e0e4ecb6
|
|
|
|
|
|
|
| |
Since our helpers now raise by default if the subcommand fails, these
will never actually fail and are not necessary.
https://github.com/rubygems/rubygems/commit/6153b9321e
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ruby_core has an 'ast.rb' file that gets in the
middle and breaks this spec, so it's better we skip
this test on this workflow for now.
Also, slightly change the spec name from "run" to
"runs" and change the last assertion, it's cleaner
to check empty error.
Thanks to David Rodríguez for this!
Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>
https://github.com/rubygems/rubygems/commit/ba8eaa70c3
|
|
|
|
|
|
|
|
|
|
|
|
| |
With older versions of rubocop, the dependency on
`jaro_winkler` seems to be a pain.
However, in the later versions of rubocop, this
dependency was dropped. So we only need to use
the older version for ruby2.3.
Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>
https://github.com/rubygems/rubygems/commit/9cd87eaee3
|
|
|
|
|
|
|
|
|
|
|
| |
because rubocop configuration inheritance is
messed up and when using `--ignore-parent-exclusion`,
even though the exit status is 0, the example
still fails because of the configuration issue.
Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>
https://github.com/rubygems/rubygems/commit/3e20b2738c
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The later RuboCop versions don't work with ruby2.3
so we should lock the version to what works with
ruby2.3 as we haven't dropped the support yet.
And since we're using the older version of rubocop,
also fix `Max` value of `LineLength` to 120, which
is the current standard. Without this, rubocop
will throw the line length offenses.
Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>
https://github.com/rubygems/rubygems/commit/46d0a800a2
|
|
|
|
|
|
| |
Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>
https://github.com/rubygems/rubygems/commit/83e330fa87
|
|
|
|
|
|
|
|
|
| |
With this, it will be ensured that the generated
(skeleton) gem will have no offenses.
Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>
https://github.com/rubygems/rubygems/commit/47411262e0
|
|
|
|
|
|
|
|
|
|
| |
Previously, we were using the old syntax like:
`task :default => :spec`, but now this commit
uses the new Ruby 1.9 hash syntax.
Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>
https://github.com/rubygems/rubygems/commit/b41d0fdb56
|
|
|
|
|
|
| |
Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>
https://github.com/rubygems/rubygems/commit/730b770f8a
|
|
|
|
|
|
| |
Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>
https://github.com/rubygems/rubygems/commit/e2ee0b7de3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
File.readlines
Using File.open without a block leaves a file reference that causes issues with file operations
commands/binstubs_spec.rb
install/gems/compact_index_spec.rb
install/gems/dependency_api_spec.rb
install/gems/standalone_spec.rb
runtime/executable_spec.rb
https://github.com/rubygems/rubygems/commit/4b9a6ca156
|
|
|
|
|
|
|
|
|
|
|
|
| |
Windows skip
Added one skip for:
bundle binstubs <gem>
when the gem exists in the lockfile
when generating bundle binstub outside bundler
should abort
https://github.com/rubygems/rubygems/commit/b77b484889
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/4f519638ae
|
|
|
|
|
|
| |
Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>
https://github.com/rubygems/rubygems/commit/ef2dae4222
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, there is no `.rubocop.yml` shipped by default.
So when a user runs `rubocop` after creating a new gem via
`bundle gem foo`, it throws a bunch of offenses.
With the default `.rubocop.yml` present, the number of those
offenses significantly reduce by 25.
Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>
|
|
|
|
|
|
| |
Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>
https://github.com/rubygems/rubygems/commit/ef2dae4222
|
| |
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/e3f60d8aec
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/a73fa0760e
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/f52733f6a4
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/4d1a0c465a
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/746a4b3d74
|
|
|
|
|
|
| |
errors
https://github.com/rubygems/rubygems/commit/6bac832a58
|
|
|
|
|
|
| |
creation
https://github.com/rubygems/rubygems/commit/9e5f7a9099
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/2af2abe5fd
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/288f073c3c
|
|
|
|
|
|
|
|
| |
consistent
* Add hints for --ci option
https://github.com/rubygems/rubygems/commit/5f779f45b0
|
|
|
|
|
| |
Co-authored-by: Olle Jonsson <olle.jonsson@gmail.com>
https://github.com/rubygems/rubygems/commit/24f3739585
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/80571452ca
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/d8e416d89b
|
|
|
|
|
|
| |
* `bundle gem` has new option to select CI provider
https://github.com/rubygems/rubygems/commit/320f3546c1
|
|
|
|
|
|
| |
* `bundle gem` has new option to choose CI provider other than Travis CI
https://github.com/rubygems/rubygems/commit/afaecf16de
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/22cb599bcc
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/80260b3496e357bf96ffe6f381e29bf25b6749cb
|
|
|
|
|
|
|
| |
These specs doesn't really need an installed bundle, they only need a
`Gemfile`.
https://github.com/rubygems/rubygems/commit/06c85683ae
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/ade0c441d5
|
|
|
|
|
|
|
|
|
| |
This spec is specifically testing for the case where there's no
`Gemfile.lock` file and it's only doing the expected thing because the
`bundle install` command is silently failing. Remove the `bundle
install` to reduce confusion.
https://github.com/rubygems/rubygems/commit/ec39fbde0e
|
|
|
|
|
|
|
| |
They don't need to run that many commands, and the new version is also
more readable in my opinion.
https://github.com/rubygems/rubygems/commit/efff3e3210
|
|
|
|
|
|
|
| |
They are preceded by `install_gemfile` calls, which mean `bundle
install` is being run twice for no reason.
https://github.com/rubygems/rubygems/commit/d2b2d10862
|
|
|
|
|
|
|
|
|
|
| |
This command is failing because of the same reason that the subsequent
`bundle exec` is failing: the gemspec is invalid. The `bundle install`
here deviates the `bundle exec` focus from the test and is unnecessary:
all we need is a `Gemfile` that will trigger the `bundle exec`, so let's
create and avoid the extra command.
https://github.com/rubygems/rubygems/commit/eb83cf6cf1
|
|
|
|
|
|
|
| |
This command was silently failing but doesn't really affect the outcome
of the spec.
https://github.com/rubygems/rubygems/commit/7880d08146
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It turns out that this test is checking essentially nothing useful. The
paperclip gem doesn't exist in our setup, so initial install is failing
and the test is only checking that calling `bundle check` 3 times on a
broken setup always returns the same thing.
I went to the history of this test:
* https://github.com/rubygems/bundler/commit/105654a31e07e9b0a198f1a5a5ec94e365854edf
* https://github.com/rubygems/bundler/commit/ae53be1f8748bfc41bc6565dc4922a1c0ac80998
* https://github.com/rubygems/bundler/commit/d19f4a7b32ccf4ec4ecda5c7c0354adc81e1efb6
* https://github.com/rubygems/bundler/commit/092f169d01472336598e29b32550399991940d63
* https://github.com/rubygems/bundler/commit/36878435b5f0be75fc6f2e07cebd7f15aaddadf0
And have finally decided to remove it since I'm not sure changing it to
something else will lead to testing something useful and not already
tested.
https://github.com/rubygems/rubygems/commit/6184322967
|