Skip to main content

Posts

GIT : forking workflow

Forking Workflow  : https://www.atlassian.com/git/workflows The Forking Workflow is fundamentally different than the other workflows discussed in this tutorial. Instead of using a single server-side repository to act as the “central” codebase, it gives every  developer a server-side repository. This means that each contributor has not one, but two Git repositories: a private local one and a public server-side one.  

clone a single branch from git repo

git clone -b <branch> --branch <branch> --single-branch git://github/repository.git --[no-]single-branch Clone only the history leading to the tip of a single branch, either specified by the  --branch  option or the primary branch remote's  HEAD  points at. When creating a shallow clone with the  --depth option, this is the default, unless  --no-single-branch  is given to fetch the histories near the tips of all branches. Further fetches into the resulting repository will only update the remote-tracking branch for the branch this option was used for the initial cloning. If the HEAD at the remote did not point at any branch when  --single-branch  clone was made, no remote-tracking branch is created.

Go Google Go! A Language on Full Throttle

InfoWorld (12/18/13) Serdar Yegulalp   Go, Google's C-like language, recently was ranked at the top of TechEmpower's eighth round of Web framework benchmarks. Go proved to be the strongest in the JSON serialization test, achieving the best peak performance and the lowest latency scores. The high performance with JSON serialization indicates that Go is being performance-tuned for the same set of workloads most directly associated with frameworks such as Node.js. Node.js' lowest performance was at 14.3 percent of Go's speed, while the best was at 69.1 percent. Node.js has the advantage of a broad software development culture--not just through its package repository, but also because there are many more JavaScript programmers than there are Go programmers. Another newcomer in the benchmarks is Facebook's HipHop PHP VM (HHVM), an open source project that compiles PHP into C++ instead of interpreting it. HHVM was designed to replace Facebook's existing PHP-execution...

HOWTO remove all dangling commits from your git repository

A good explanation of the dangling ( fr: ballants) commits source tells you how they get created. git fsck --full   Checking object directories: 100% (300/300), done. Checking objects: 100% (10658/10658), done. dangling commit x.... dangling blob y.... dangling commit z.... dangling blob w.... dangling blob a.... dangling commit b.... How to quickly remove those? git reflog expire --expire=now --all git gc --prune=now

push and delete remote branches

This is an action that many Git users need to do frequently, but many (including the me!!) have forgotten how to do so or simply don’t know how. Here’s the definitive guide if you’ve forgotten. For this reason I put it on my dev site on cofares the with free articles resources galaxy of sites. So you have checked out a new branch, committed some awesome changes, but now you need to share this branch though with another developer. You can push the branch up to a remote very simply: git push origin <pascal> Where origin is your remote name and <pascal> is the name of the branch you want to push up. Deleting is also a pretty simple task: git push origin :<pascal> That will delete the newfeature branch on the origin remote, but you’ll still need to delete the branch locally with   git branch -d <pascal>