rspec-dev
rspec-dev copied to clipboard
rspec
RSpec development environment
This PR introduces more JRuby versions to the build matrix.
Hello I always look at the best way to start contributing to RSpec. I think rspec-dev is full of powerfull rake commands but lack of documentation to properly start hacking...
This may or may not be serious, depending on how thread-safe you consider RSpec itself to be, but it did lead to some red herring bugs in JRuby and Rubinius...
Hello As mentioned in this comment : https://github.com/rspec/rspec-rails/pull/2231#issuecomment-567930499 > I would love to be able to more easily run the build locally, and run each step without looking at shell...
- [ ] Draft blog post (?) - [x] Checkout the latest code and get bundles current - `rake change_branch[master]` - [x] Update changelogs in all repos - Add version...
It's common for us to create a branch and open a PR in one repo (e.g. rspec-support) and also create a branch and open a PR in another repo (e.g....
It would be great to get our rake task updated so that any changes to our CoC are propagated to both [rspec/rspec](https://github.com/rspec/rspec) and [rspec/rspec-dev](https://github.com/rspec/rspec-dev). Related, perhaps we should include the...
Quoting @dchelimsky from rspec/rspec.github.io#70: > Lastly, and I realize this is a bit of work (though it could probably be automated), I'd turn the names of all the contributors to...