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
+5-11Lines changed: 5 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,12 @@
1
-
# Contributing to electiondata development
2
-
3
-
The goal of this guide is to help you get up and contributing to electiondata as
4
-
quickly as possible. The guide is divided into two main pieces:
5
-
6
-
1. Filing a bug report or feature request in an issue.
7
-
1. Suggesting a change via a pull request.
8
-
9
1
Please note that electiondata is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md).
10
2
By contributing to this project,
11
3
you agree to abide by its terms.
12
4
13
-
## Issues
5
+
# Contributing to electiondata development
6
+
7
+
## Report a Problem
14
8
15
-
When filing an issue, the most important thing is to include a minimal
9
+
To report a problem, [file an issue on GitHub](https://github.com/ElectionDataAnalysis/electiondata/issues). When filing an issue, the most important thing is to include a minimal
16
10
reproducible example so that we can quickly verify the problem, and then figure
17
11
out how to fix it. Please include
18
12
@@ -32,7 +26,7 @@ You can check you have actually made a reproducible example by:
32
26
1. if files or folders were moved by the system to the archive directory, move them back to the input directory, removing any timestamps from directory names.
33
27
1. navigating to the working directory, calling python, and producing the behavior in question.
34
28
35
-
## Pull requests
29
+
## Revise the Code
36
30
37
31
To contribute a change to `electiondata` follow these steps:
0 commit comments