-
Notifications
You must be signed in to change notification settings - Fork 47
/
repos-feature-usage.html
55 lines (54 loc) · 1.44 KB
/
repos-feature-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
---
layout: default
title: Repositories
permalink: /repos-feature-usage
---
<div class="chart-placeholder">
<h3>Repository Feature Usage</h3>
<canvas
data-url="{{ site.dataURL }}/repository-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 with at least one active <a href="https://help.github.com/articles/about-protected-branches/">protected branch</a> and at least one <a href="https://help.github.com/articles/about-topics/">topic</a> assigned to them.
</p>
<p>
In this context, <em>active</em> designates repositories with at least one pushed commit in the last four weeks.
</p>
<p>
All shared branches (for example, master and release branches) should be protected to ensure that they cannot be deleted or rewritten by accident.
Furthermore, tagging repository with associated topics increases their discoverability.
</p>
</div>
</div>