I chose to use the git versions and use git to make my own -dev branch of a few modules to troubleshoot the interaction of Views and Draggableviews modules, because. This I've also tested, recently, because I found it useful to label my current working brach different than the remote master branch of the same name. The -dev branch label is not present in the branch command output unless you put it there yourself in your local cloned repository. Now its finally possible to understand the -dev branch in Drupal as the 'development snapshot' created from the 'master' branch of the git branch hosted at. 'A Drupal development snapshot is created from a git branch, while a Drupal release is created from a git tag.' Instead of git tag try with git branch.'Īnd yet, still won't say what I'm about to say. Now, returning the helpful advise I've received to this point.

Its a strange example to find at the maintainers site, adding a remote repository without any commits, but in the Land of Oz customization to the nth degree is a known hazzard. 'Now, the reason you wouldn't have a master branch even after doing a git init is that there are no commits: when you create your first commit, you will then have a master branch.' stackoverflow: 'fatal: Not a valid object name: 'master'' Fortunately this mystery was quickly solved by creating my own test repository and a subsequent search at Stackoverflow confirms this is technically true, a new git repository without any commits does not have a master branch: If there is a master branch? That does not suggest 'every' git repository has a 'master'. So, if there is a master branch on the server, you can access the log of that branch locally.' git-scm 'In the default case that is automatically written by a git remote add command, Git fetches all the references under refs/heads/ on the server and writes them to refs/remotes/origin/ locally. And here I turned to a site search at the maintainers site,, to find this gem: In my novice git-ucation, I wasn't sure if 'master' was also a naming convention of developers or built into the git application itself. Now, you'll have to bear with me for a moment as I digress. And here is the principal issue I've been working on in this post: relating a convention (developer convention, programming best practice, or The Drupal Way) to the operation and use of the git application. Now we have a definitive statement describing a convention for active development on the 'master version'. 'You can choose either the latest stable version or the master version, but keep in mind the master version may have bugs since developers are actively working on it.' PHPMaster An article describes setting up 'your own Git repository viewer' on a local repository (for developers who prefer to not host in the cloud), There is a sense -dev is equivalent to rough draft in the familiar metaphor of writing. This is my attempt to clarify this with a reasoned, but in no sense authoritative, definition: Simply because it does not appear using the commands $git branch or $git tag while -dev clearly is evident in the 'Development releases' table on a module's main page. Yet, a key second part of any answer must include a translation of the Drupal -dev naming convention. On, you cannot create a Drupal release from a git tag similar to beta-release, or a Drupal snapshot from a git branch similar to test-branch.ĮDIT: As pointed out, the question was 'How do I git pull a dev branch' which has been partially demonstrated in the other answers. Tags similar to 7.x-3.0 (or 7.x-3.1-beta3) are for the 7.x-3 version of a module, and its development snapshot is named 7.x-3.x-dev. In your case the development snapshot is 7.x-3.x-dev, and the git branch is 7.x-3.x.įurthermore, the git tag used to create a Drupal release must follow a specific schema. The name of the git branch is the name of the Drupal development snapshot without the -dev part. To make it clear: A Drupal development snapshot is created from a git branch, while a Drupal release is created from a git tag. the development snapshot 7.x-3.x-dev for the Views module) from for the first time is executing the following command: git pull git clone -recursive -branch 7.x-3.x Īfter that, if you need to keep the local repository for the Views module updated, you should execute the following commands: cd views The way to pull the repository for the 7.x-3.x branch of the Views module (i.e.

Workign with dev and origin master git