git

Using Git to manage both a core repo and project-specific repos

I am currently using git to manage my site-specific projects, e.g. code that lives under /sites in a multisite (single core) scenario.

However, I find myself needing to work on two things that will require a separate repository tracking the Drupal core: 1) one-off core patches, and 2) install profiles.

5 comments · Read more
mig5's picture

Video of Gordon's presentation on Git and Drupal, Melbourne, September 09

Gordon's presentation on Git and Drupal from 8th September at the regular Melbourne Drupal meet @Emspace, has been uploaded to blip.tv by realityloop, who also did a fine job of recording it.

Here's the link.

Thanks Gordon, and thanks Brian for organising, recording, and uploading :)

1 comment
awebb's picture

Presentation on managing Drupal projects with Git and GitHub

I just thought I post a little information about a presentation I am going to be giving at the October meetup. At the last meetup, I was asked if I would mind giving a presentation on the use of GitHub in managing Drupal projects. We have pretty much switched all of our development versioning to Git at CollectiveColors.com, because it has shown to have significant benefits in our own development processes.

Git makes it easier for us because:

  1. It allows us to better collaboratively develop our software while minimizing the impact of code conflicts.
  2. Allows us to easily track what we have developed.
  3. Branching and merging of repositories is a breeze.
  4. It is very easy to turn any directory tree into a Git repository.
  5. Git submodules are perfect for Drupal development.

We have learned a lot of really cool methods for managing software projects using Git and GitHub, so we figured that we would share some of what we have learned in our journey so far. Although, I have a rough outline of what I want to talk about during this presentation, I am open to hearing your suggestions, after all I'm not presenting to myself.

So what I am thinking so far? ...

3 comments · Read more
anarcat's picture

Aegir code (and drush!) now accessible through git

I have finally got around tackling git-cvsimport. After a little bit of tweaking around, I've been able to import the entire history of the various Aegir projects on Drupal.org in our git repositories. This will enable much easier collaboration and decentalised development.

4 comments · Read more
jpetso's picture

Git scrutinized

There's a great introduction on git for SVN people like me, which made it twice as easy for me to look into how this thing works. Git only recently released their 1.5 version which is the first one that's supposed to be usable to the masses. (It might not yet be available pre-packaged for your Linux distribution, or available at all if you're running Windows, which could be a small hurdle at the beginning.) After reading the introductory couse and trying it out by myself, I must say I'm hooked.

For those who didn't know, git is the distributed RCS that was created by Linus and the other kernel folks because they needed to get rid of BitKeeper, and as the Linux kernel is a very demanding project both in code size and in patch management, git is quite capable indeed from an efficiency point of view. Currently in use by the Linux kernel itself, X.org, Wine, and One Laptop Per Child, to name a few popular projects.

As promised in my SoC application, here's a short rundown of features that are important to this abstraction layer.

11 comments · Read more
Syndicate content