Working with Github clones and local repos: Cloud9 IDE

I recently tried using the Cloud9 online IDE. It starts by creating a clone of your Github repo. My regular local use of git is fairly simple (init, status, commit, push to Github, branch, edit, pull, merge…), but because I don’t usually clone, I haven’t got my autopilot head around how to:

  • push changes made in my C9 clone back to the original repo in Github.

this outline guide suggests using the same username for github and C9, but a no-clutter step-by-step is what I’m looking for…

  • How can I push changes directly from Cloud9 IDE to Heroku?
  • Cloud9 git push -> fatal: Authentication failed
  • Git push to DigitalOcean from Bitbucket or Cloud9
  • How to push to github from cloud9?
  • How do I show just the names and commit titles since a tag in Git?
  • Git pull over SSH - Repository not found. HTTPS works
  • What is your way to keep binary dependencies in the version control system?
  • Can “git pull” automatically stash and pop pending changes?
  • bad sha1 files handling
  • How to migrate from Subversion to Mercurial when the trunk/branch/tag structure is a mess?
  • 2 Solutions collect form web for “Working with Github clones and local repos: Cloud9 IDE”

    If you auth with your Github account in cloud9 and clone a Github project, then if you git push it will push to the original repo in Github

    [JJ] If you cloned the project in Cloud9 before (via the command line, so not via the UI on the dashboard), you can do git remote add upstream git@github.com:your/repo.git. Now you have another remote that you can either pull from (git pull upstream master or push to git push upstream master).

    Commit as usual using the C9 CLI, then simply run git push from the C9 CLI, as you would normally when developing on your machine.

    Git Baby is a git and github fan, let's start git clone.