This repository was archived by the owner on Nov 30, 2024. It is now read-only.
File tree Expand file tree Collapse file tree 2 files changed +19
-5
lines changed Expand file tree Collapse file tree 2 files changed +19
-5
lines changed File renamed without changes.
Original file line number Diff line number Diff line change 19
19
20
20
## Contributing
21
21
22
- 1 . Fork it
23
- 2 . Create your feature branch (` git checkout -b my-new-feature ` )
24
- 3 . Commit your changes (` git commit -am 'Add some feature' ` )
25
- 4 . Push to the branch (` git push origin my-new-feature ` )
26
- 5 . Create new Pull Request
22
+ Once you've set up the environment, you'll need to cd into the working
23
+ directory of whichever repo you want to work in. From there you can run the
24
+ specs and cucumber features, and make patches.
25
+
26
+ NOTE: You do not need to use rspec-dev to work on a specific RSpec repo. You
27
+ can treat each RSpec repo as an independent project.
28
+
29
+ - [ Build details] ( BUILD_DETAIL.md )
30
+ - [ Code of Conduct] ( CODE_OF_CONDUCT.md )
31
+ - [ Detailed contributing guide] ( CONTRIBUTING.md )
32
+ - [ Development setup guide] ( DEVELOPMENT.md )
33
+
34
+ ## Patches
35
+
36
+ Please submit a pull request or a github issue to one of the issue trackers
37
+ listed below. If you submit an issue, please include a link to either of:
38
+
39
+ * a gist (or equivalent) of the patch
40
+ * a branch or commit in your github fork of the repo
You can’t perform that action at this time.
0 commit comments