You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,7 @@
1
1
## How can I help?
2
2
3
+
Everyone is encouraged to open issues that are affecting you: bugs, ideas, performance problems – everything helps!
4
+
3
5
The first place to start is by looking at our [GitHub Issues](https://github.com/rails-api/active_model_serializers/issues).
4
6
5
7
The vast majority of development is happening under the `master` branch, currently slated for release as `0.10.x`. This is where we would suggest you start.
@@ -20,6 +22,10 @@ AMS uses a subset of [StandardIssueLabels](https://github.com/wagenet/StandardIs
20
22
21
23
1. Fork it ( https://github.com/rails-api/active_model_serializers/fork )
22
24
2. Create your feature branch (`git checkout -b my-new-feature`)
23
-
3. Commit your changes (`git commit -am 'Add some feature'`)
24
-
4. Push to the branch (`git push origin my-new-feature`)
25
-
5. Create a new Pull Request
25
+
3. Write tests for your feature, or regression tests highlighting a bug
26
+
4. Write the feature itself, or fix your bug
27
+
5. Commit your changes (`git commit -am 'Add some feature'`)
28
+
6. Push to the branch (`git push origin my-new-feature`)
29
+
7. Create a new Pull Request
30
+
31
+
Remember to squash your commits and rebase off `master`.
0 commit comments