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/PULL_REQUEST_TEMPLATE.md
+27-1Lines changed: 27 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,33 @@ Please be aware that the Selenium Grid 3.x is being deprecated in favour of the
3
3
upcoming version 4.x. We won't be receiving any PRs related to the Grid 3.x code. Thanks!
4
4
-->
5
5
6
+
**Thanks for contributing to Selenium!**
7
+
**A PR well described will help maintainers to quickly review and merge it**
6
8
9
+
Before submitting your PR, please check our [contributing](https://github.com/SeleniumHQ/selenium/blob/master/CONTRIBUTING.md) guidelines.
10
+
Avoid large PRs, help reviewers by making them as simple and short as possible.
7
11
8
12
9
-
-[ ] By placing an `X` in the preceding checkbox, I verify that I have signed the [Contributor License Agreement](https://github.com/SeleniumHQ/selenium/blob/master/CONTRIBUTING.md#step-6-sign-the-cla)
13
+
<!--- Provide a general summary of your changes in the Title above -->
14
+
15
+
### Description
16
+
<!--- Describe your changes in detail -->
17
+
18
+
### Motivation and Context
19
+
<!--- Why is this change required? What problem does it solve? -->
20
+
21
+
### Types of changes
22
+
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
23
+
-[ ] Bug fix (non-breaking change which fixes an issue)
24
+
-[ ] New feature (non-breaking change which adds functionality)
25
+
-[ ] Breaking change (fix or feature that would cause existing functionality to change)
26
+
27
+
### Checklist
28
+
<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
29
+
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
30
+
-[ ] I have read the [contributing](https://github.com/SeleniumHQ/selenium/blob/master/CONTRIBUTING.md) document.
31
+
-[ ] My change requires a change to the documentation.
32
+
-[ ] I have updated the documentation accordingly.
33
+
-[ ] I have added tests to cover my changes.
34
+
-[ ] All new and existing tests passed.
35
+
<!--- Provide a general summary of your changes in the Title above -->
(or CLA). We ask this so that we know that contributors have the right
190
-
to donate the code.
191
-
192
-
When you open your pull request we ask that you indicate that you've
193
-
signed the CLA. This will reduce the time it takes for us to integrate
194
-
it.
195
-
196
-
### Step 7: Push
185
+
### Step 8: Push
197
186
198
187
```shell
199
188
% git push origin my-feature-branch
@@ -208,7 +197,7 @@ comments to address, apply your changes in new commits (preferably
208
197
[fixups](http://git-scm.com/docs/git-commit)) and push to the same
209
198
branch.
210
199
211
-
### Step 8: Integration
200
+
### Step 9: Integration
212
201
213
202
When code review is complete, a committer will take your PR and
214
203
integrate it on Selenium's master branch. Because we like to keep a
@@ -250,3 +239,4 @@ Issues are labelled to make them easier to categorise and find by:
250
239
Selenium contributors frequent the `#selenium` channel on
251
240
[`irc.freenode.org`](https://webchat.freenode.net/). You can also join
252
241
the [`selenium-developers@` mailing list](https://groups.google.com/forum/#!forum/selenium-developers).
242
+
Check https://selenium.dev/support/ for a complete list of options to communicate.
0 commit comments