# Cloning git repository and pulling changes from sage updates

**URL:** https://discourse.roots.io/t/cloning-git-repository-and-pulling-changes-from-sage-updates/10552
**Category:** sage
**Tags:** sage8
**Created:** 2017-09-30T10:03:56Z
**Posts:** 6
**Showing post:** 4 of 6

## Post 4 by @fullyint — 2017-09-30T18:11:16Z

> [@ralphonz](#):
>
> how would you go about merging an updated version of sage into your project?

If you’re merging a super simple bug fix from upstream Sage, you could do it by hand, of course. For approaches that better use the power of git you could see this note about cherry picking Sage commits:

> [@Sage 9 parent/child theme](https://discourse.roots.io/t/sage-9-parent-child-theme/8696/2):
>
> Sage isn’t set up to be a parent/child theme, it’s a starter theme you build from. I do agree that with Sage 9 especially being in active development, you will want to keep it updated. I would suggest adding the Sage repo as another git repo on your project, and then you can cherry pick commits from it. Something like this: [https://gist.github.com/kalenjohnson/9ed257d8afb81e571a4b](https://gist.github.com/kalenjohnson/9ed257d8afb81e571a4b) Going off memory, something like this: git add sage git@github.com:roots/sage.git git fetch sage git cherry-pick -…

---

_[View the full topic](https://discourse.roots.io/t/cloning-git-repository-and-pulling-changes-from-sage-updates/10552)._