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: using/product/reputation.md
+39-15
Original file line number
Diff line number
Diff line change
@@ -65,21 +65,22 @@ By default, `12` reputation is awarded when a pull request is merged that was op
65
65
66
66
Depending on the content of the pull request, a maintainer can award more (or less) reputation by adding one of the following labels to the pull request:
|`x:size/tiny`| 3 | <ul><li>Fixing a single typo or link</li><li>Removing a blank line or adding a line break</li><li>Changing/adding a single code comment</li></ul> |
71
-
|`x:size/small`| 5 | <ul><li>Fixing a single test case, task or example</li><li>Fixing multiple typos or links in a single file</li><li>Clarifying content by adding a few lines to a file</li></ul> |
72
-
|`x:size/medium`| 12 | <ul><li>Syncing an exercise with problem-specifications (incl. edits)</li><li>Adding one or more test cases from scratch</li><li>Improving multiple files in an exercise</li><li>Adding mentor notes for an exercise from scratch</li><li>Fixing a small bug in a test runner/analyzer/representer</li><li>Adding analyzer comments for a single exericse</li></ul> |
73
-
|`x:size/large`| 30 | <ul><li>Adding a new concept or practice exercise</li><li>Adding new concept documentation</li><li>Substantial re-writing of an existing concept or exercise</li><li>Adding new CI scripts or other automation</li></ul> |
74
-
|`x:size/massive`| 100 | <ul><li>Creating a test-runner, analyzer, representer or generator from scratch</li><li>Major refactors to those tools</li><li>Creating major documentation from scratch (e.g. contribution or testing guides)</li></ul> |
|`x:rep/tiny`| 3 | <ul><li>Fixing a single typo or link</li><li>Removing a blank line or adding a line break</li><li>Changing/adding a single code comment</li></ul> |
71
+
|`x:rep/small`| 5 | <ul><li>Fixing a single test case, task or example</li><li>Fixing multiple typos or links in a single file</li><li>Clarifying content by adding a few lines to a file</li></ul> |
72
+
|`x:rep/medium`| 12 | <ul><li>Syncing an exercise with problem-specifications (incl. edits)</li><li>Adding one or more test cases from scratch</li><li>Improving multiple files in an exercise</li><li>Adding mentor notes for an exercise from scratch</li><li>Fixing a small bug in a test runner/analyzer/representer</li><li>Adding analyzer comments for a single exericse</li></ul> |
73
+
|`x:rep/large`| 30 | <ul><li>Adding a new concept or practice exercise</li><li>Adding new concept documentation</li><li>Substantial re-writing of an existing concept or exercise</li><li>Adding new CI scripts or other automation</li></ul> |
74
+
|`x:rep/massive`| 100 | <ul><li>Creating a test-runner, analyzer, representer or generator from scratch</li><li>Major refactors to those tools</li><li>Creating major documentation from scratch (e.g. contribution or testing guides)</li></ul> |
75
75
76
76
The examples above can serve as rough orientation when to apply which label but maintainers are free to use their own judgement.
77
77
78
+
- The estimated number of time spent should be interpreted as the average time a _maintainer_ would spend on doing the PR.
78
79
- If more than one label is specified, the label with the highest reputation value determines the awarded reputation.
79
80
- If a pull request is still open, no reputation is awarded (yet).
80
81
- If a pull request is closed _without_ merging, no reputation is awarded.
81
82
82
-
Note that an `x:size` label on an **issue** never affects the awarded reputation - even if a merged pull request lacks an `x:size`label, and closes an issue that has one.
83
+
_For backwards compatibility purposes, we also support using the `x:size`labels to determine the awarded reputation._
83
84
84
85
### Reviewing a pull requests
85
86
@@ -91,16 +92,21 @@ For each merged or closed pull request reviewed by the user, `5` reputation is a
91
92
92
93
- The reputation awarded for a pull request review changes if one of the following labels are added to the pull request:
93
94
94
-
| Label | Reputation |
95
-
| ---------------- | ---------- |
96
-
|`x:size/tiny`| 1 |
97
-
|`x:size/small`| 2 |
98
-
|`x:size/medium`| 5 |
99
-
|`x:size/large`| 10 |
100
-
|`x:size/massive`| 20 |
95
+
| Label | Reputation |
96
+
| --------------- | ---------- |
97
+
|`x:rep/tiny`| 1 |
98
+
|`x:rep/small`| 2 |
99
+
|`x:rep/medium`| 5 |
100
+
|`x:rep/large`| 10 |
101
+
|`x:rep/massive`| 20 |
102
+
103
+
It is _not_ possible to use different reputation "sizes" for a pull request author and reviewer.
104
+
Both are based on the same `x:rep` label.
101
105
102
106
If more than one label is specified, the label with the highest reputation value determines the awarded reputation.
103
107
108
+
_For backwards compatibility purposes, we also support using the `x:size` labels to determine the awarded reputation._
109
+
104
110
### Merging a pull request
105
111
106
112
For each pull request that was merged by the user, `1` reputation is awarded.
@@ -109,3 +115,21 @@ For each pull request that was merged by the user, `1` reputation is awarded.
109
115
- If a pull request is closed _without_ merging, no reputation is awarded.
110
116
- The user that opened the pull request does _not_ get reputation for merging their own pull request.
111
117
- If the pull request does not have any reviews, `5` reputation is awarded instead.
118
+
119
+
### Opening an issue
120
+
121
+
Like pull requests, by default, **no reputation is awarded** when an issue is opened.
122
+
Unlike pull requests, reputation is only awarded for large or massive issues.
123
+
124
+
Depending on the content of the issue, a maintainer can choose to award reputation by adding one of the following labels to the issue:
0 commit comments