@@ -9,6 +9,14 @@ let you know so that you can rebase it.
9
9
> ** Note** : To contribute code to Docker projects, see the
10
10
[ Contribution guidelines] ( opensource/project/who-written-for ) .
11
11
12
+ ### Files not edited here
13
+
14
+ Files and directories listed in the ` path: ` keys in
15
+ [ ` .NOT_EDITED_HERE.yaml ` ] ( /NOT_EDITED_HERE.yaml ) are maintained in other
16
+ repositories and should not be edited in this one. Pull requests against these
17
+ files will be rejected. Make your edits to the files in the repository and path
18
+ in the ` source: ` key in the YAML file.
19
+
12
20
### Quickstart
13
21
14
22
If you spot a problem while reading the documentation and want to try to fix it
@@ -79,10 +87,42 @@ The following `vnext` branches currently exist:
79
87
docs for upcoming features in the [ docker/kitematic] ( https://github.com/docker/kitematic/ )
80
88
project
81
89
90
+ ## Collaborate on a pull request
91
+
92
+ Unless the PR author specifically disables it, you can push commits into another
93
+ contributor's PR. You can do it from the command line by adding and fetching
94
+ their remote, checking out their branch, and adding commits to it. Even easier,
95
+ you can add commits from the Github web UI, by clicking the pencil icon for a
96
+ given file in the ** Files** view.
97
+
98
+ If a PR consists of multiple small addendum commits on top of a more significant
99
+ one, the commit will usually be "squash-merged", so that only one commit is
100
+ merged in. On occasion this is not appropriate and all commits will be kept
101
+ separate when merging.
102
+
103
+ ## Pull request guidelines
104
+
105
+ Help us review your PRs more quickly by following these guidelines.
106
+
107
+ - Try not to touch a large number of files in a single PR if possible.
108
+
109
+ - Don't change whitespace or line wrapping in parts of a file you are not
110
+ editing for other reasons. Make sure your text editor is not configured to
111
+ automatically reformat the whole file when saving.
112
+
113
+ - A Netlify test runs for each PR that is against one of our long-lived
114
+ branches like ` master ` and the ` vnext ` branches, and deploys the result of
115
+ your PR to a staging site. The URL will be available at the bottom of the PR
116
+ in the ** Conversation** view. Check the staging site for problems and fix them
117
+ if necessary. Reviewers will check the staging site too.
118
+
119
+ If you can think of other ways we could streamline the review process, let us
120
+ know.
121
+
82
122
## Style guide
83
123
84
- If you have questions about how to write for Docker's documentation, please see
85
- the [ style guide] ( https://docs.docker.com/opensource/doc-style/ ) . The style guide provides
86
- guidance about grammar, syntax, formatting, styling, language, or tone. If
87
- something isn't clear in the guide, please submit an issue to let us know or
88
- submit a pull request to help us improve it.
124
+ If you have questions about how to write for Docker's documentation, have a look
125
+ at the [ style guide] ( https://docs.docker.com/opensource/doc-style/ ) . The style
126
+ guide provides guidance about grammar, syntax, formatting, styling, language, or
127
+ tone. If something isn't clear in the guide, please submit an issue to let us
128
+ know or submit a pull request to help us improve it.
0 commit comments