@@ -19,20 +19,6 @@ RSpec repos as well. Add the following to your `Gemfile`:
19
19
end
20
20
```
21
21
22
- ## Contributing
23
-
24
- Once you've set up the environment, you'll need to cd into the working
25
- directory of whichever repo you want to work in. From there you can run the
26
- specs and cucumber features, and make patches.
27
-
28
- NOTE: You do not need to use rspec-dev to work on a specific RSpec repo. You
29
- can treat each RSpec repo as an independent project.
30
-
31
- * [ Build details] ( BUILD_DETAIL.md )
32
- * [ Code of Conduct] ( CODE_OF_CONDUCT.md )
33
- * [ Detailed contributing guide] ( CONTRIBUTING.md )
34
- * [ Development setup guide] ( DEVELOPMENT.md )
35
-
36
22
## Basic Structure
37
23
38
24
RSpec uses the words "describe" and "it" so we can express concepts like a conversation:
@@ -376,6 +362,20 @@ Finished in 0.000379 seconds
376
362
1 example, 0 failures
377
363
```
378
364
365
+ ## Contributing
366
+
367
+ Once you've set up the environment, you'll need to cd into the working
368
+ directory of whichever repo you want to work in. From there you can run the
369
+ specs and cucumber features, and make patches.
370
+
371
+ NOTE: You do not need to use rspec-dev to work on a specific RSpec repo. You
372
+ can treat each RSpec repo as an independent project.
373
+
374
+ * [ Build details] ( BUILD_DETAIL.md )
375
+ * [ Code of Conduct] ( CODE_OF_CONDUCT.md )
376
+ * [ Detailed contributing guide] ( CONTRIBUTING.md )
377
+ * [ Development setup guide] ( DEVELOPMENT.md )
378
+
379
379
## Also see
380
380
381
381
* [ https://github.com/rspec/rspec ] ( https://github.com/rspec/rspec )
0 commit comments