diff options
| author | JuanitoFatas <katehuang0320@gmail.com> | 2016-08-26 23:34:16 +0800 |
|---|---|---|
| committer | JuanitoFatas <katehuang0320@gmail.com> | 2016-08-26 23:34:16 +0800 |
| commit | 6667a9d9a1fd7f83b4d262ff00b933f8574a974f (patch) | |
| tree | e394a15f2c9327dc1e32c4b0969dafb72702135b | |
| parent | a4a5f1c53156e85c597e9938f08e874930199957 (diff) | |
| download | bundler-6667a9d9a1fd7f83b4d262ff00b933f8574a974f.tar.gz | |
Add a note on how to dive into the code with Pry [ci skip]
Follow up of https://github.com/bundler/bundler/pull/4919#issuecomment-242706463
| -rw-r--r-- | DEVELOPMENT.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md index 8964b75c3d..ab95db363a 100644 --- a/DEVELOPMENT.md +++ b/DEVELOPMENT.md @@ -40,6 +40,8 @@ Bundler doesn't use a Gemfile to list development dependencies, because when we The `BUNDLE_DISABLE_POSTIT` environment variable ensures that the version of Bundler in `/path/to/bundler/lib` will be used. Without that environment setting, Bundler will automatically download, install, and run the version of Bundler listed in `Gemfile.lock`. With that set up, you can test changes you've made to Bundler by running `dbundle`, without interfering with the regular `bundle` command. +To dive into the code with Pry: `RUBYOPT=-rpry dbundle` to require pry and then run commands. + # Submitting Pull Requests Before you submit a pull request, please remember to do the following: |