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

Read full article as PDF:

Related content

  • 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.

  • Git 101

    When several people collaborate on source code or documents, things can get messy fast. Git provides a quick cure: The distributed versioning system reliably ensures the integrity and consistency of data with minimal effort.

  • Perl: Travis CI

    A new service on travis-ci.org picks up GitHub projects, runs new code through test suites, and notifies the owners if the build fails. Its API enables Perl scripts to gather historical build data, including who-broke-the-build tabulations.

  • Command Line: Vundle

    If you use Vim, you'll likely need a tool to manage its hundreds of plugins. Vundle can help.

  • Copy Files on a Local Network with bcp
comments powered by Disqus

Direct Download

Read full article as PDF:

News