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-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,19 @@
1
1
# Contributing to atomate
2
+
2
3
We love your input! We want to make contributing to atomate as easy and transparent as possible, whether it's:
4
+
3
5
* Reporting a bug
4
6
* Discussing the current state of the code
5
7
* Submitting a fix
6
8
* Proposing or implementing new features
7
9
* Becoming a maintainer
8
10
9
11
## Reporting bugs, getting help, and discussion
12
+
10
13
At any time, feel free to start a thread on our [Discourse forum](https://discuss.matsci.org/c/atomate).
11
14
12
15
If you are making a bug report, incorporate as many elements of the following as possible to ensure a timely response and avoid the need for followups:
16
+
13
17
* A quick summary and/or background
14
18
* Steps to reproduce - be specific! **Provide sample code.**
15
19
* What you expected would happen, compared to what actually happens
@@ -19,16 +23,19 @@ If you are making a bug report, incorporate as many elements of the following as
19
23
We love thorough bug reports as this means the development team can make quick and meaningful fixes. When we confirm your bug report, we'll move it to the GitHub issues where its progress can be further tracked.
20
24
21
25
## Contributing code modifications or additions through Github
22
-
We use github to host code, to track issues and feature requests, as well as accept pull requests. We maintain a list of all contributors to atomate [here.](https://atomate.org/contributors.html)
26
+
27
+
We use github to host code, to track issues and feature requests, as well as accept pull requests. We maintain a list of all contributors to atomate [here](https://atomate.org/contributors.html).
23
28
24
29
Pull requests are the best way to propose changes to the codebase. Follow the [Github flow](https://www.atlassian.com/git/tutorials/comparing-workflows/forking-workflow) for more information on this procedure.
25
30
26
31
The basic procedure for making a PR is:
32
+
27
33
* Fork the repo and create your branch from main.
28
34
* Commit your improvements to your branch and push to your Github fork (repo).
29
35
* When you're finished, go to your fork and make a Pull Request. It will automatically update if you need to make further changes.
30
36
31
37
### How to Make a **Great** Pull Request
38
+
32
39
We have a few tips for writing good PRs that are accepted into the main repo:
33
40
34
41
* Use the Google Code style for all of your code. Find an example [here.](https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html)
@@ -41,4 +48,5 @@ When you submit your PR, our CI service will automatically run your tests.
41
48
We welcome good discussion on the best ways to write your code, and the comments on your PR are an excellent area for discussion.
42
49
43
50
#### References
51
+
44
52
This document was adapted from the open-source contribution guidelines for Facebook's Draft, as well as briandk's [contribution template](https://gist.github.com/briandk/3d2e8b3ec8daf5a27a62).
0 commit comments