RSpec at github

April 9th, 2008

After a few months of exploring git and hosting RSpec’s git repository at github, we’re happy to announce that github is now RSpec’s official home for Source Code Management.

<p>Tracking will continue to live at the <a href="http://rspec.lighthouseapp.com">lighthouse</a>.</p>


<p>We will continue to release gems to <a href="Rubyforge">http://rubyforge.org/projects/rspec</a>, but we will no longer be committing changes to the subversion repository there. For Rails users who are using the rspec plugins for Rails, edge rails now supports git-hosted plugins.</p>


<p>We&#8217;ve broken the project up into four separate repositories:</p>


<ul>
<li><a href="http://github.com/dchelimsky/rspec/wikis/home">rspec</a> for the rspec gem/plugin</li>
    <li><a href="http://github.com/dchelimsky/rspec-rails/wikis/home">rspec-rails</a> for the rspec-rails gem/plugin (formerly rspec_on_rails)</li>
    <li><a href="http://github.com/dchelimsky/rspec-tmbundle/wikis/home">rspec-tmbundle</a> for the TextMate bundle</li>
    <li><a href="http://github.com/dchelimsky/rspec-dev/wikis/home">rspec-dev</a> for developers/contributors</li>
</ul>


<p>See the wikis for each repository for more information about building, installing and contributing to the project.</p>

8 Responses to “RSpec at github”

  1. Ryan Heneise Says:

    Great to hear! I have been watching for Rspec on Github and just recently moved my rspec plugins over to git submodules.

    <p>I love Github! Every time I watch a new repository I think of Meet the Parents &#8211; &#8220;I&#8217;m watching you Focker&#8221; (points two fingers at eyes).</p>
    
  2. nicholas a. evans Says:

    Unfortunately, the git-submodule command (needed for rspec-dev, as per http://github.com/dchelimsky/rspec-dev/wikis/contributingpatches) seems to be missing in git version 1.5.2.5 (Ubuntu 7.10). Oh well, Ubuntu 8.4 will be released in a couple of weeks… perhaps it’s time for me to upgrade to the beta.

    <p>I don&#8217;t think that I&#8217;ll be able to refrain from comments about trendy git-hype, or unfavorable feature/usability comparisons to bzr or darcs&#8230; but hey, for a vibrant open source project any <span class="caps">DVCS</span> is better than no <span class="caps">DVCS</span>!   ;-)</p>
    
  3. Thomas Maurer Says:

    @nicholas: try to build git yourself. it’s really damn easy :), you just need some basic dev tools installed.

    <p>@david: just added rspec as submodule to my rails projects and wanted to tie it to the latest stable release. but there isn&#8217;t any tag in your github repo :((. could you at least add one for the last rspec release? would be nice.</p>
    
    
    <p>thanks.</p>
    
  4. Thomas Maurer Says:

    ah @david: perhaps you just missed to run `git push—tags` to push the tags to the remote repo. that doesn’t happen by a plain push.

  5. David Chelimsky Says:

    @thomas: Unfortunately, that tag was back when there was a single repository. I could tag the repos, but you’d end up with vendor/plugins/rspec/rspec and vendor/plugins/rspec/rspec_on_rails.

    <p>If you want that release, you&#8217;re going to have to continue to use subversion at rubyforge until we do the 1.1.4 release.</p>
    
  6. David Chelimsky Says:

    @nicholas – we bailed on submodules so you should be OK now

  7. Anny Says:

    I have wanted one of these forever! THANKS for the great work

  8. nicholas a. evans Says:

    @david: and just after I’ve upgraded too. ;)