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: .github/CONTRIBUTING.md
+6-8Lines changed: 6 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,8 +16,6 @@ Note that your contributions must be your own work and licensed under the same t
16
16
## Reporting bugs
17
17
18
18
First, search the issue tracker to see if the bug is already there.
19
-
Please use the [discussion forums](https://oxyplot.userecho.com/) if you are unsure whether it is a bug in the library or a problem in your code.
20
-
When you are sure, please add defects in the issue tracker.
21
19
22
20
It is very helpful to get the generated code (use `CTRL+ALT+C` in the plot control) and report (`CTRL+ALT+R`) of the bug plot. You can also take a screen shot and paste it into the description.
23
21
@@ -36,8 +34,9 @@ A bug report should include:
36
34
37
35
## Suggesting new features
38
36
39
-
Please use the [discussion forums](https://oxyplot.userecho.com/) or add it directly in the issue tracker in the same way as bug reports.
37
+
First, search the issue tracker to see if the feature is already there.
40
38
39
+
Wait for some feedback before starting to work on something that might not be merged in the end.
41
40
42
41
## Create your own fork
43
42
@@ -96,26 +95,25 @@ Finally, push your commits: `git push`
96
95
97
96
## Requirements for a pull request
98
97
98
+
- Include the issue number
99
99
- Include examples or unit tests for the change / new feature
100
100
- Update the CHANGELOG.md file
101
101
- Update the CONTRIBUTORS and AUTHORS files if you are not already listed there
102
-
- Commits are rebased and squashed
103
102
104
103
105
104
## Creating a pull request
106
105
107
106
- Open the GitHub page for your fork and create a "Pull Request" (PR)
108
-
- Include the issue number in the pull request *comment* (not in the *title* where it will not be linked!)
109
107
110
108
111
109
## Merging
112
110
113
-
When the PR is submitted, Appveyor will build the code and report if the build was successful.
111
+
When the PR is submitted, a build will automatically be trigged.
114
112
A team member will then review the PR, and merge the branch if everything looks OK.
115
113
116
-
If there are some issues with the PR, you must
114
+
If there are some issues with the PR, you should
117
115
- update your code and commit changes
118
-
- rebase and squash again
116
+
-clean up the git history with rebase or squash
119
117
- force push: `git push -f`
120
118
121
119
The PR will be updated automatically when you push your changes.
0 commit comments