User login

Home ›
 project

project

Maintaining a Drupal project with Git: Vacating the master branch

Submitted by Benjamin Melançon on June 22, 2012 - 10:15am
in

If you've already been committing code to master, do this to start a new 7.x branch and kill off the code in the master branch so noone gets confused.

cd /path/to/repo
git checkout -b 7.x-1.x

git push origin 7.x-1.x

git checkout master
git rm -r *
echo "Real code is not kept on the master branch, to see the code: git checkout 7.x-1.x" > README.txt
git add README.txt
git commit -m "Add a README explaining that the master branch is empty."
git push origin master

Use Git to commit to CVS, such as for maintaining a Drupal module

Submitted by Benjamin Melançon on July 20, 2009 - 2:34pm
in

UPDATE: See http://more.zites.net/git_drupal_contrib_cvs

Kathleen says this is complicated and not necessary - http://drupal.org/node/288873

HOWEVER-- if you ever want to let other people contribute to your project the normal way (if CVS can be considered in any way normal), then you will want the synch anyway.

Syndicate content