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: docs/content/community/contributing.md
+26-38
Original file line number
Diff line number
Diff line change
@@ -12,56 +12,44 @@ title: Contributing to Hugo
12
12
weight: 30
13
13
---
14
14
15
-
All contributions to Hugo are welcome. Whether you want to scratch an itch, or simply contribute to the project, feel free to pick something from the roadmap
16
-
or contact [spf13](http://spf13.com) about what may make sense
17
-
to do next.
15
+
To contribute to the project *we encourage pull requests allowing for discussion of code changes.*
18
16
19
-
You should fork the project and make your changes. *We encourage pull requests to discuss code changes.*
17
+
## Contributing
20
18
19
+
When you are ready to send us a pull request make sure you perform the following steps first.
21
20
22
-
When you're ready to create a pull request, be sure to:
21
+
* Ensure you have at least one test case that covers the new code. If you are wondering how to do this please feel free to ask in the pull request for help.
22
+
* Ensure you run the tests. `node test/runner.js -t functional`
23
+
* Squash all your commits into a single commit. `git rebase -i`. You can force update your pull request as history for it is not important for us to keep.
23
24
24
-
* Have test cases for the new code. If you have questions about how to do it, please ask in your pull request.
25
-
* Run `go fmt`
26
-
* Squash your commits into a single commit. `git rebase -i`. It's okay to force update your pull request.
27
-
* Make sure `go test ./...` passes, and `go build` completes. Our Travis CI loop will catch most things that are missing. The exception: Windows. We run on Windows from time to time, but if you have access, please check on a Windows machine too.
25
+
## Contribution Steps
28
26
29
-
## Contribution Overview
27
+
1. Fork the Node.js driver from https://github.com/mongodb/node-mongodb-native
28
+
2. Create a new feature branch (`git checkout -b feature`)
29
+
3. Commit your changes using git (`git commit -a -m 'My changes'`)
30
+
4. Run tests suite (ensure mongodb is in path) (`node test/runner.js -t functional`)
31
+
5. Squash the commits (`git rebase -i`)
32
+
6. Push the new branch to your github fork (`git push origin feature`)
33
+
7. Create a new Pull Request on github.
30
34
31
-
1. Fork Hugo from https://github.com/spf13/hugo
32
-
2. Create your feature branch (`git checkout -b my-new-feature`)
33
-
3. Commit your changes (`git commit -am 'Add some feature'`)
34
-
4. Commit passing tests to validate changes.
35
-
5. Run `go fmt`
36
-
6. Squash commits into a single (or logically grouped) commits (`git rebase -i`)
37
-
7. Push to the branch (`git push origin my-new-feature`)
0 commit comments