git

Hi all,

I'm looking at (finally) getting around to using GIT, mainly to keep a history of theme changes.

Just wondering if people could share their opinions on what should be stored in the repositories. I've seen everything from people just storing the theme they are working on to the entire Drupal install (minus the settings.php file).

I was considering just the sites folder, but I'm wondering if maybe I should go for the entire Drupal install?

What are people's views?

Cheers,
Chris

Une vidéo et un article pour revenir sur la notion de déploiement Drupal.
Cette méthode exploite l'outil d'intégration continue "Jenkins" et la possibilité d'Aegir de changer un site de plateforme (master/distribution)

• "Zero-touch Drupal deployment with Jenkins, Aegir, Git, Fabric and Drush"
• http://mig5.net/node/342

Voici les slides de la présentation sur GIT, discutée dans le dernier Drupal meetup du groupe Suisse-Romande.

Les ressources citées :

GIT - http://git-scm.com
Tutoriel site du zéro - http://www.siteduzero.com/tutoriel-3-254198-gerez-vos-codes-source-avec-...
Pro Git - http://progit.org
GIT cheatsheet - http://www.ndpsoftware.com/git-cheatsheet.html (<-- nice !)
Github - http://github.com

Buenas gente.

LLevo varios días intentado subir varios módulos (nuevos y actualizaciones), incluyendo el módulo dedicado a la legislación española (LOPD) ;) Y no hay manera de hacerlo.

He leido, re-leido la documentación, y creo que lo estoy haciendo bien, pero esta claro de que no lo estoy haciendo bien porque tal y como se ve en el gitweb de Drupal http://drupalcode.org/project/imagecache_static.git no se han subido/compartido los archivos.

Hi all,

I'm a total newbie working on git, trying to set up version control with drupal. Hope this a right place to ask... otherwise just kick me off.

My aim is to use an external service (either bettercodes or gitenterprise) to host a remote repository for my drupal projects.

i followed the instruction on this page : http://drupal.org/node/803746
I success only If i just grab a tar.gz from d.o, set up locally, then push to the remote repo.

In case i take my drupal copy from git.drupal.org, perform the same operations, then push, i obtain these errors (gitenterprise)

git has replaced cvs as the version control system for drupal. -

There is a number of articles on to how handle git
but they don't really address the needs of site maintainers.
I am aware that this is a developers' group but since I found no better place to turn to...
... let me git it a try, anyway.

I have found no article specifically dealing with the needs of drupal admins
when having to MOVE FROM CVS TO GIT ON PRODUCTIVE SITES.

Let me ask a couple of questions as a site admin on Linux systems
on what to do in order to successfully move to git.

--> Actually I am going to tell you how I used to do things via cvs
hoping to get hands-on tips on how to do them via git.

I recently posted this tiny post on how to delete remote tags from a Git repository. http://himer.us/kY2imV

I always have the problem (with my Drupal repositories) that I will accidentally send a tag labeled like: 7.x-3.x-beta1, and it should actually be 7.x-3.0-beta1. Every time I needed to try to replace that tag, I was having to search the internet again for the exact syntax to remove those incorrectly named tags from the Drupal repository.

I'll likely be trying to post a lot more git tips and tricks in the near future.

I was reading the site builders guide to Git (http://drupal.org/node/803746) and had a question about renaming remotes across all environments. The guide indicates to only rename the remote on your local development environment to point to your new repository.

When I update/commit/push to my new repository everything is fine, but when I pull to my development or staging environment and run git status, I get a notice that my branch is ahead of origin/xxxxxxx by 3 commits.

Should I rename the remotes in all environments to point to my repository as origin??

Hello,

I am a lazy developer.

Could we have a file upload field on our project page on drupal.org, where we can upload a zip file and that would take care of all the committing the code to the project? :D

I am pretty sure a large percentage of the projects on Drupal are one man shows, and I believe it would be sufficient for a lot of devs. :) In the backend of course there still would be git...

Would be sweet.

Git, CVS, ssh, drush is all great stuff. But sometimes I just wish I wouldn't have to care. :P