|1blankspace||All js files including master.js||Standard viewport (user views) interaction (controller) files - eg manage a contact person that is binding the CONTACT endpoint. As used at 1blankspace.com|
|1blankspace-developer||js files for the simple developer interface (IDE)||The files for managing website/apps, structures etc - as used in developer.1blankspace.com|
|1blankspace-winrt||Win8/RT example enterprise app.||Visual Studio 2012 Expresss RC Solution files.|
You can fork either repository to build your own app and then pull down the master incrementally as changes are made to it - with out effecting your own fork.
if you have some great sample code you want to show or re-use then gist it.
Basic Git Workflow Example
Thanks to heroku.
Using git bash:
Initialize a new git repository, then stage all the files in the directory and finally commit the initial snapshot.
$ git init
$ git add .
$ git commit -m 'initial commit'
Create a new branch named featureA, then check it out so it is the active branch. then edit and stage some files and finally commit the new snapshot. $ git branch featureA
$ git checkout featureA
$ (edit files)
$ git add (files)
$ git commit -m 'add feature A'
Switch back to the master branch, reverting the featureA changes you just made, then edit some files and commit your new changes directly in the master branch context.
$ git checkout master
$ (edit files)
$ git commit -a -m 'change files'
Merge the featureA changes into the master branch context, combining all your work. Finally delete the featureA branch.
$ git merge featureA
$ git branch -d featureA
Example as a ibcom/1blankspace repository owner with ssh key access:
$ git remote add origin email@example.com:ibcom/1blankspace.git
$ git pull origin master
$ git push -u origin master
Remove files that have been deleted:
$ git add -u
$ git commit
|Github Getting Started|
|Git cheat sheet|
|Register your apps as mashups on programmableweb.com|