This page was machine translated. Please help us improve it.
Make sure you have read:
Then, follow these steps to fix a failing spec:
rake
to ensure that all CI specs are passing.bin/mspec spec/some/spec_file.rb
to confirm the spec fails.rake build
to build your change.bin/mspec spec/some/spec_file.rb
to see if your change makes the
spec pass.rake
to ensure there are no regressions.git status, git add, git commit
, etc. Any changes made to the spec
files under the spec/ruby directory must be in a different commit from
changes made to other Rubinius source code files.git format-patch origin
, which will extract commits that the current
branch accumulated since the last pull from origin, or `git format-patch
-N’, where N is the number (1, 2, etc.) of commits for which you want to
generate patches.When your patch is accepted by the Rubinius project, you’ll get a commit bit for the Rubinius repository. Let Evan know what your Github username is.