Migrating open source code repositories from CVS to GitHub

Pitfalls!

Remember that GitHub publishes every detail of your project work: If you enjoy writing insulting code comments or commit log messages, it's a good idea to stop doing so and clean up the repository before publishing it; GitHub will post whatever you write as search engine fodder. Things that were previously only accessible to a few developers in a hidden CVS repository are now suddenly available to your grandma and grandpa on a normal HTML page. Before you commit, make sure you take a close look at the content.

Infos

  1. Listings for this article: ftp://www.linux-magazin.de/pub/listings/magazin/2009/08/Perl
  2. "The PITA Threshold: GitHub vs. CPAN" by Dan Dascalescu, http://wiki.dandascalescu.com/essays/pita-threshold
  3. "Turn your Sourceforge Project into a Git Repo" by Mike Schilli, March 21, 2009, http://blog.usarundbrief.com/?p=12

« Previous 1 2 3 4

Buy Linux Magazine

SINGLE ISSUES
Print Issues
Digital Issues
 
SUBSCRIPTIONS
Print Subs
Digisubs
 
TABLET & SMARTPHONE APPS
Get it on Google Play

US / Canada

Get it on Google Play

UK / Australia

Related content

  • GitHub with hub

    The handy hub command-line tool lets you manage your GitHub repository from a terminal window, which can make it easier to automate repetitive tasks.

    more »
  • Perl: CMS with GitHub

    With its easy-to-use web interface, GitHub can be put to totally different uses than archiving code. For example, Perlmeister Mike Schilli used GitHub to deploy a content management system for simple websites.

    more »
  • Branch Management

    Git makes version control as simple as possible. To manage your Git branches successfully, you need to learn the ins and outs of git branch and git merge.

    more »
  • Workspace: GitBook

    Write and publish ebooks with the GitBook software and publishing platform.

    more »
  • Tree View

    Complex Git projects sometimes require a better view of the dependencies and branches. Several tools offer GUI options for Git. We take a look at gitk, gitg, git-gui, and GitAhead.

    more »
comments powered by Disqus