delta/gitlab/gitlab-ce.git/scripts, branch pre-commit-prettier

Add check if run from gitlab development kit root directory.

2018-01-02T21:01:45+00:00

Check for symlink instead of file before install.

2018-01-02T20:57:45+00:00

Update script to work only when run in the gitlab directory.

2018-01-02T20:49:39+00:00

Remove `-f` to not ruin other people's existing pre-commit files.

2017-12-20T20:54:21+00:00

Add changelog and newlines

2017-12-20T20:48:45+00:00

Add script to enable code formatters

2017-12-20T20:29:27+00:00

Remove JSX since we don't use it.

2017-12-20T20:19:09+00:00

Initial install

2017-12-20T17:09:22+00:00

Preserve gem path so that we use the same gems

2017-12-19T09:41:59+00:00

Without this patch, I would end up with:

```
An error occurred in a `before(:suite)` hook.
Failure/Error: raise "could not connect to gitaly at #{socket.inspect} after #{sleep_time} seconds"

RuntimeError:
  could not connect to gitaly at "tmp/tests/gitaly/gitaly.socket" after 10 seconds
```

Digging into it, it's because `scripts/gitaly-test-spawn` could not
spawn the process, because it cannot find the installed gems.

I personally installed all my gems under $HOME, namely with:

* `gem install rake --user-install` or:
* `bundle install --path ~/.gem`

The gems would be installed to `~/.gem/ruby/2.4.0/gems`, where
the version is Ruby ABI version.

Now we're changing $HOME, making RubyGems think that the gems
would be installed to `tmp/tests/ruby/2.4.0/gems` which is
apparently not the case.

In order to workaround this, we could preserve $GEM_PATH
populated by RubyGems, ignoring the default path based on $HOME.

Make rubocop happy

2017-12-15T05:59:52+00:00