# Updating to the Latest Version of JumpStart Pro

DevFeed: [Updating to the Latest Version of JumpStart Pro](<https://devfeed.tech/articles/updating-to-the-latest-version-of-jumpstart-pro-28249.md>)

Original publisher: [Read original article](<http://fuzzyblog.io/blog/rails/2019/12/29/updating-to-the-lastest-version-of-jumpstart-pro.html>)

Author: Fuzzygroup

Published: 2019-12-29T00:00:00Z

Content type: tutorial

Language: en

Sources: [Scott Johnson](<https://devfeed.tech/sources/scott-johnson.md>)

Topics: [Git](<https://devfeed.tech/topics/git.md>), [GitLab](<https://devfeed.tech/topics/gitlab.md>), [Rails](<https://devfeed.tech/topics/rails.md>), [repo](<https://devfeed.tech/topics/repo.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [Development](<https://devfeed.tech/topics/development.md>)

Tags: [development](<https://devfeed.tech/tags/development.md>), [git](<https://devfeed.tech/tags/git.md>), [github](<https://devfeed.tech/tags/github.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [jumpstart](<https://devfeed.tech/tags/jumpstart.md>), [rails](<https://devfeed.tech/tags/rails.md>), [repo](<https://devfeed.tech/tags/repo.md>)

## AI overview

A tutorial on updating JumpStart Pro projects by cloning the source repository, configuring separate remotes, and pushing project changes. It explains how copying a project without its .git directory disconnected the project from the original remote and prevented normal updates.

## Source excerpt

So I've been using JumpStart Pro to build a new side project and in a discussion with Chris Oliver, the creator of JumpStart Pro, I reported a bug which he said "Oh - you should update to the latest". He viewed the update process as something seamless and I, honestly, didn't get it. And, in researching this, I discovered that I made a fatal mistake. The rest of this blog post covers that mistake and explains how you update JumpStart Pro. Here's the tldr (too long; did not read): ALWAYS, ALWAYS, ALWAYS create a new app based on JumpStart Pro by cloning it from the GitLab source i.e. you start with: "git clone git@gitlab.com:gorails/jumpstart-pro.git YOUR_PROJECT_NAME" Go to github and create a repo for YOUR_PROJECT_NAME Copy the github clone info and add it as a separate remote: git remote add YOUR_PROJECT_NAME git@github.com:YOUR_GITHUB_USERNAME/YOUR_PROJECT_NAME.git Make a change like updating the README.md and do the add / commit dance and push to your repo as git push YOUR_PROJECT_NAME master Even though I've worked with Git for more than a decade now, I've previously only worked with Heroku as a git remote so I missed the implications of this when I originally cloned my first JumpStart Pro app. Sigh. The critical mistake I made was that I had started my second JumpStart Pro project by copying from the first JumpStart Pro project I had made and the NOT moving over the .git folder. This meant that my new project was now disconnected from the original remote so I couldn't just do a git pull to update it. Fixing My Own Stupidity Here's what I did to fix this: I started by creating a new application cloning into a new location: git clone git@gitlab.com:gorails/jumpstart-pro.git okrsnow I created a new git repo for my app I added the new repo with: git remote add okrsnow git@github.com:fuzzygroup/okrsnow.git I made a change and pushed to git push okrsnow master I manually copied over all the code from my original JumpStart pro repo. Given that Rails apps have such a c