diff options
| author | zachel <zach@zachel.io> | 2023-01-26 15:03:45 +0900 |
|---|---|---|
| committer | Drew DeVault <sir@cmpwn.com> | 2023-01-26 08:43:27 +0100 |
| commit | a0a3d8f1e7862e58e74574cde171ef58e5ed5179 (patch) | |
| tree | b97de40f5045f07595bb2b801db5acbe4e7bea76 /tutorials/builds.sr.ht/github-integration.md | |
| parent | 4c197644df9988caa9f639b27ad53faadb35c18d (diff) | |
| download | sr.ht-docs-a0a3d8f1e7862e58e74574cde171ef58e5ed5179.tar.gz | |
Remove all references to dispatch.sr.ht
This patch removes remaining references to dispatch.sr.ht
that were left inside the docs after dispatch.sr.ht was
removed (commit aea6609d9595)
Diffstat (limited to 'tutorials/builds.sr.ht/github-integration.md')
| -rw-r--r-- | tutorials/builds.sr.ht/github-integration.md | 34 |
1 files changed, 2 insertions, 32 deletions
diff --git a/tutorials/builds.sr.ht/github-integration.md b/tutorials/builds.sr.ht/github-integration.md index a26806f..c5f4056 100644 --- a/tutorials/builds.sr.ht/github-integration.md +++ b/tutorials/builds.sr.ht/github-integration.md @@ -100,38 +100,9 @@ different names for packages, different distributions of coreutils, and so on. ## Adding these builds to your GitHub repository -Try making a new "mrsh" repository on your GitHub account. Note that forks won't -work — so make sure you make a *new* repository and push the mrsh code to it. -Take a look at the `.builds` directory in mrsh: each of these build manifests -can be submitted on push or pull request by rigging up a dispatch.sr.ht task. +Since 2022-10-01, dispatch.sr.ht is now deprecated. -Go to [dispatch.sr.ht](https://dispatch.sr.ht) and "Configure new task". Pick -"GitHub commits > builds.sr.ht jobs" and click "Add task" for your new mrsh -repository. That's all you have to do! Now let's make a dummy commit and push it -to GitHub to test it out: - - git commit --allow-empty -m "Testing builds.sr.ht" - git push - -Head over to your [builds.sr.ht dashboard](https://builds.sr.ht) and you should -see your build begin momentarily! - -## Testing pull requests on GitHub - -If you want to run your CI against pull requests on GitHub, follow a similar -procedure, but select "GitHub pull requests > builds.sr.ht jobs" instead. Then, -each new pull request that comes into your repo will be built on builds.sr.ht -and the pull request status updated with the build results. - -## Why doesn't my GitHub repo show up? - -There are a couple of limitations: - -- Forks are not supported -- You must have admin access to the repo (test this by trying to add a webhook - through the GitHub UI manually) - -If neither of these are the issue, [write us an email](mailto:sir@cmpwn.com). +See [hottub](https://sr.ht/~emersion/hottub) for third-party integration. --- @@ -144,4 +115,3 @@ Other resources: - [builds.sr.ht user manual](/builds.sr.ht) - [Build manifest reference](/builds.sr.ht/manifest.md) -- [dispatch.sr.ht](/dispatch.sr.ht) |