From 552e9e2299286c97cfa3568cea69e7decd2ff848 Mon Sep 17 00:00:00 2001 From: Brian Morearty Date: Thu, 29 Jan 2015 13:34:44 -0800 Subject: [PATCH] Doc: run bundle update after cloning Rails. --- guides/source/contributing_to_ruby_on_rails.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/guides/source/contributing_to_ruby_on_rails.md b/guides/source/contributing_to_ruby_on_rails.md index 7381521658..e06706d750 100644 --- a/guides/source/contributing_to_ruby_on_rails.md +++ b/guides/source/contributing_to_ruby_on_rails.md @@ -173,6 +173,14 @@ $ git checkout -b my_new_branch It doesn't matter much what name you use, because this branch will only exist on your local computer and your personal repository on GitHub. It won't be part of the Rails Git repository. +### Bundle Update + +Update and install the required gems. + +```bash +$ bundle update +``` + ### Running an Application Against Your Local Branch In case you need a dummy Rails app to test changes, the `--dev` flag of `rails new` generates an application that uses your local branch: -- GitLab