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: submitting-a-pull-request.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ layout: default
10
10
11
11
## Long Version
12
12
13
-
You don't have to wait until all your work is done in order to send us a pull request. If you want the core team to look at your code, but not accept the changes yet, open a pull request, and prefix the title with 'WIP'. That tells us to review the code, but that it is not done, and is not yet ready to merge. When you are finished, and the PR is ready to merge, simply remove 'WIP' from the PR tktle, and we'll give it a final look, and merge it.
13
+
You don't have to wait until all your work is done in order to send us a pull request. If you want the core team to look at your code, but not accept the changes yet, open a pull request, and prefix the title with 'WIP'. That tells us to review the code, but that it is not done, and is not yet ready to merge. When you are finished, and the PR is ready to merge, simply remove 'WIP' from the PR title, and we'll give it a final look, and merge it.
14
14
15
15
When you submit a pull request, an automated build (using AppVeyor) will merge your changes onto a copy of the master repository, build that configuration, and run all automated tests. If any of those steps fail, we will ask you to fix them before we accept the pull request. (We don't comment on this if you've labelled the PR 'WIP'.)
0 commit comments