blob: 5a233e9cf9d30ff1e327c5763fcc93f1d9c64cf2 (
plain) (
blame)
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
|
---
title: GitHub integration
---
dispatch.sr.ht supports various integrations with [GitHub](https://github.com).
Some tips are provided here.
# Configuration
When setting up a new GitHub task on dispatch.sr.ht, your GitHub repositories
will be shown for selection. This list only contains repositories for which
you are the owner. Repositories that are forks of another GitHub repo are
not available for dispatch.sr.ht tasks due to GitHub API limitations.
# Build environment
dispatch.sr.ht will check out the specific commit you pushed when submitting
builds, and will rewrite the upstream clone URL to the fork when building pull
requests.
## Configuring your sources list
Do not include `.git` at the end of your git clone URLs.
## Environment variables
The following environment variables are set when building commits:
- `GITHUB_DELIVERY`: the webhook delivery UUID that triggered this build
- `GITHUB_EVENT`: the event type ("push") that triggered this build
- `GITHUB_REF`: the ref (e.g. "refs/heads/master") that was updated
- `GITHUB_REPO`: the full name (e.g. "username/repo_name") of the GitHub repo
The following environment variables are set when building pull requests:
- `GITHUB_DELIVERY`: the webhook delivery UUID that triggered this build
- `GITHUB_EVENT`: the event type ("push") that triggered this build
- `GITHUB_PR_NUMBER`: the pull request number
- `GITHUB_PR_TITLE`: the title of the pull request
- `GITHUB_BASE_REPO`: the full name (e.g. "username/repo_name") of the base repo
- `GITHUB_HEAD_REPO`: the full name (e.g. "username/repo_name") of the head repo (fork)
# Configuring branch protection rules on GitHub
If you choose the "auto-merge" setting, builds.sr.ht will attempt to merge the
pull request once the build completes successfully. You will likely want to add
branch protection rules on GitHub to prevent this from happening before the pull
request is reviewed.
To edit your branch protection rules, start by visiting "Branches" in your
repository's settings.
Select "Add rule".
Specify the branches you want the rule to apply to (e.g. "master") and configure
the criteria which must be met for the pull request to be mergeable. For
example, to require the code to be reviewed before merge:
**Important**: if your account is an administrator on this GitHub repository,
attempts to merge will succeed *even if the branch protection rules are unmet*.
You must enable the "Include administrators" option to prevent this.
|
