-
Notifications
You must be signed in to change notification settings - Fork 47
/
pr-usage.html
68 lines (67 loc) · 1.63 KB
/
pr-usage.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
---
layout: default
title: Pull Request usage in %
permalink: /pr-usage
---
<div class="chart-placeholder">
<h3>Pull Request Usage</h3>
<canvas
data-url="{{ site.dataURL }}/pull-request-usage.tsv"
data-type="history"
data-config='{
"views":
[
{
"label": "2 m",
"tooltip": "Show the last 2 months",
"aggregate": false,
"slice": [0, 61]
},
{
"label": "2 y",
"tooltip": "Show the last 2 years",
"aggregate":
{
"period": "week",
"method": "median"
},
"slice": [0, 106],
"default": true
},
{
"label": "all",
"tooltip": "Show all data",
"aggregate":
{
"period": "week",
"method": "median"
}
}
]
}'></canvas>
<div class="info-box">
<p>
The percentage of active repositories located in organizations, having more than one contributor, and using pull requests for contributions.
</p>
<p>
In this context, <em>active</em> designates repositories with at least two users that have pushed commits in the last four weeks.
The rationale behind this is that pull request usage is most important in a collaborative environment.
</p>
<p>
High pull request usage might indicate a high number of code reviews.
</p>
</div>
<div class="info-box">
<p>
For reference, the percentage of status usage in these pull requests is visualized.
</p>
<p>
High status usage might indicate high CI usage.
</p>
</div>
<div class="info-box">
<p>
Repositories in personal accounts and repositories with a single contributor are ignored, as they are less likely to use pull requests.
</p>
</div>
</div>