-
Notifications
You must be signed in to change notification settings - Fork 19
/
Copy pathindex.html
81 lines (69 loc) · 3.55 KB
/
index.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
69
70
71
72
73
74
75
76
77
78
79
80
81
<!doctype html>
<html>
<head>
<meta charset="utf-8">
<title>Homu</title>
<style>
* { font-family: sans-serif; }
code { font-family: monospace; }
h1 { font-size: 22px; }
h2 { font-size: 18px; }
h3 { font-size: 16px; }
h4 { font-size: 14px; }
p, ul { font-size: 15px; line-height: 150%; }
code { background-color: #efefef; }
body { max-width: 60em; margin-left: auto; margin-right: auto; }
.repos { font-size: 18px; line-height: 180%; }
</style>
</head>
<body>
<h1>Homu</h1>
<h2>Repositories</h2>
<ul class="repos">
{% for repo in repos %}
<li><a href="queue/{{repo}}">{{repo}}</a></li>
{% endfor %}
</ul>
<hr>
<h2>Homu Cheatsheet</h2>
<h3>Commands</h3>
<p>
Here's a quick reference for the commands Homu accepts. Commands must be posted as
comments on the PR they refer to. Comments may include multiple commands. Homu will
only listen to official reviewers that it is configured to listen to. A comment
must mention the GitHub account Homu is configured to use. (e.g. for the Rust project this is @bors)
</p>
<ul>
<li><code>r+ (SHA)</code>: Accept a PR. Optionally, the SHA of the last commit in the PR can be provided as a guard against synchronization issues or malicious users. Regardless of the form used, PRs will automatically be unaccepted if the contents are changed.</li>
<li><code>r=NAME (SHA)</code>: Accept a PR on the behalf of NAME.</li>
<li><code>r-</code>: Unacccept a PR.</li>
<li><code>p=NUMBER</code>: Set the priority of the accepted PR (defaults to 0).</li>
<li><code>rollup</code>: Mark the PR as likely to merge without issue, implies <code>p=-1.</code></li>
<li><code>rollup-</code>: Unmark the PR as <code>rollup</code>.</li>
<li><code>retry</code>: Signal that the PR is not bad, and should be retried by buildbot.</li>
<li><code>try</code>: Request that the PR be tested by buildbot, without accepting it.</li>
<li><code>force</code>: Stop all the builds on the configured builders, and proceed to the next PR.</li>
<li><code>clean</code>: Clean up the previous build results.</li>
<li><code>delegate=NAME</code>: Allow NAME to issue all homu commands for this PR</li>
<li><code>delegate+</code>: Delegate to the PR owner</li>
<li><code>delegate-</code>: Remove the delegatee</li>
</ul>
<h4>Examples</h4>
<ul>
<li><code>@homu r+ p=1</code></li>
<li><code>@homu r+ 123456</code></li>
<li><code>@homu r=barosl rollup</code></li>
<li><code>@homu retry</code></li>
</ul>
<h3>Customizing the Queue's Contents</h3>
<p>
Homu provides a few simple ways to customize the queue's contents to fit your needs:
</p>
<ul>
<li><code>queue/rust+cargo</code> will combine the queues of the <code>rust</code> and <code>cargo</code> repos (for example).</li>
<li><a href="queue/all">queue/all</a> will combine the queues of all registered repos.</li>
<li>Rows can be sorted by column by clicking on column headings.</li>
<li>Rows can be filtered by contents using the search box (only naive substring matching supported).</li>
</ul>
</body>
</html>