#Git add remote subdirectory code

Git checkout - filename // revert a file to last commit

Git reset HEAD filename // unstage a file you didn' t mean to git add Git commit -a // skip the business of staging files, and just commit everything tracked that' s changed Git commit -m 'message' // does the commit with your comment message specified as shown Git diff // show exactly what changed IN the files in UNSTAGED files (not since last commit)įor commiting the staging area to the repository: git commit // opens an editor so you can enter a commit message. Git rm filename(s) // stage removal of a file. Git add filename(s) // Use to add new and modified to a 'staged' area to commit Tracked files can be added to a temporary “staging area” using the git add command, which are then commited to the repository with git commit.įor adding/removing files to the staging area: git status // Shows what has changed since last commit in current directory. Git has the notion of your “working tree” in which files are “tracked”. I had originally grabbed it with git clone or something like that. The clone of InqSimTest I have has now been significantly modified.

git commit -a -m 'modularized commit with missing files'.

I realized that the commit didn’t add all the new files, so…

git push, using default “simple” (which only pushes the current branch, not all of them).

git status told me I was one ahead of the origin/master, recommending git push.

git commit -a -m 'first modularized commit' to add all modified files.*.

I made sure there were no new files on the remote with git pull.

git-ignore file, because I didn’t want my sublime text projects to be included

git remote add origin git push -u origin master.

Next, followed the directions for commiting to bitbucket (git remote, etc) First Time Commit InstructionsĬommiting a Durandal/Mimosa project to source control (all in mimosa-test root level) The gist of the above is using the built-in “remote” support of git by specifying an origin for the repo with git remote.

git remote add origin ssh://url-from-instructions.

#Git add remote subdirectory code

Log into Bitbucket, create new repo, then pick “I have code I want to import”.First initialize local dir with the above commands (git init, etc).The Bitbucket Instructions for pushing your unversioned code to their repo is: Two popular repositories: GitHub and BitBucket. git that contains all of your necessary repository files - a Git repository skeleton. Creating a Git repo from existing files git init -This creates a new subdirectory named. I have a new codebase that I want to put under source control (git), and I want to have a private repo on Bitbucket.