This is an abbreviated version of what you will find at Howto - Develop with a separate RubySpec repo. Refer to The Rubinius specs for more documentation on the specs.
-
Run
bin/mspec spec/some/spec_file.rbto confirm the spec fails -
Edit a file somewhere in Rubinius (probably under the
kerneldirectory) -
Run
raketo build your change -
Run
bin/mspec spec/some/spec_file.rbto see if your spec passes - Repeat until your spec passes
-
Run
rake spec:fullORbin/mspec ci -B full.mspecto ensure there are no regressions - Change directory to Rubinius root if not already there
-
Run
git status, git add, git commit, etc. -
Run
git format-patch - Upload the patch in a ticket on the Rubinius lighthouse account
When your patch is accepted by the Rubinius project, you'll get a commit bit for the Rubinius repository. You'll also get a bit for the RubySpec repository (as long as you have a Github account and let us know your Github username).
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
0.10—69% complete
Completed 9 of 13 tickets
Pages
- Home
- FAQ
- IRC Info and Who's Who
- Releases
- Using Git
- Installation
- Getting Started
- Common Build Problems and Solutions
- Howto - Contribute
- Howto - Write a ticket
- Howto - Run my Rails app with Rubinius
- Howto - Write a Ruby spec
- Howto - Write a Rubinius spec
- Howto - Fix a failing spec
- Howto - Develop with a separate RubySpec repo
- Howto - Debug shotgun
- The Rubinius specs
- Shotgun - The Rubinius Virtual Machine
- Developer Readme
- Core Library - Coding Guidelines
- Coding Style Guide
- Contributor Platforms
- Stuff to read
- Extending Standard Library Specs
- Improve Gem Support in Rubinius
- Actors - Concurrent Rubinius
- FFI or Foreign Function Interface
- Adding Dir to C++ VM
