Repair an Apify Actor's broken Git connection - pushes to GitHub that no longer start a build, builds that fail to clone the repository, or a GitHub integration rejected as invalid or expired (for example after Apify API tokens were revoked). Use when a Git-sourced Actor stopped deploying from its repository.
95%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
A Git-sourced Actor deploys through two links, and each one breaks on its own:
Diagnose both links, repair the broken ones, then prove the chain with one push. Runs keep using the last successful build the whole time, so the Actor stays up while you work.
The steps use the Apify CLI (apify login first) and the GitHub CLI (gh). They are written for GitHub; GitLab and Bitbucket have the same two links behind different commands and screens.
Two rules hold in every step:
latest) to the head of the branch, so starting a build and pushing a commit are both deploys. Get the user's go-ahead for each.apify api GET '/v2/actors/<username>~<actor-name>'
apify api GET '/v2/actors/<username>~<actor-name>/builds?desc=true&limit=5'In versions, take the entry with sourceType: "GIT_REPO" and note its versionNumber, gitRepoUrl and buildTag. In taggedBuilds, note the build that tag points at. An Actor with no GIT_REPO version deploys with apify push and is outside this skill.
Done when you can name the version, its repository URL, and the build that is live.
Read the log of the newest build of that version:
apify api GET '/v2/actor-builds/<buildId>/log'| Log line | Clone link |
|---|---|
Cloned commit ID: <sha> | Works |
Could not read from remote repository | Broken |
A build from before the trouble started proves nothing. In that case start a fresh one (a deploy) and read its log:
apify api POST '/v2/actors/<username>~<actor-name>/builds?version=<versionNumber>'Done when a build newer than the trouble shows one of the two lines.
gh api repos/<owner>/<repo>/hooks --jq '.[] | {id, active, events, host: (.config.url | split("/")[2]), last_response_code: .last_response.code}'
gh api 'repos/<owner>/<repo>/hooks/<hookId>/deliveries?per_page=5' --jq '.[] | {delivered_at, event, status_code}'An Apify webhook has the host console-backend.apify.com (registered by Apify's GitHub App) or api.apify.com (a Build Actor webhook added by hand).
| What the repository shows | Trigger link |
|---|---|
One Apify webhook, latest push delivery 2xx | Works |
Latest push delivery 400 or 401 | Broken: Apify rejects the token in the webhook URL |
| No Apify webhook | Broken: nothing starts a build |
| Two Apify webhooks answering 2xx | Works, but every push starts two builds: the user deletes one |
Done when every Apify webhook on the repository is in one row of the table.
A private repository needs the SSH form of the Git URL plus the Actor's deployment key. The user does this:
git@github.com:<owner>/<repo>.git and save. The HTTPS form only clones public repositories.Confirm the key with gh api repos/<owner>/<repo>/keys --jq '.[] | {title, read_only, created_at}', then start a build (step 2) and read its log.
Done when a build log shows Cloned commit ID with the head of the branch.
First let Apify register the webhook itself:
apify api PUT '/v2/actors/<username>~<actor-name>/versions/<versionNumber>/build-on-push' -d '{"providerId":"github-app","enabled":true}'invalid-git-auth-token: Apify's GitHub authorization is dead. Use a Build Actor webhook instead; it depends only on the clone link.For the Build Actor webhook, the user does this:
GitHub build webhook for <repo>, and copy its value: Console shows a token's value once, at creation, so an existing token cannot be reused here.token=<the new token> and version=<versionNumber>, and delete waitForFinish from it: GitHub gives a webhook 10 seconds to answer, less than a build takes.application/json, keep Just the push event, and save.Adding the webhook makes GitHub send a ping, which starts one build: a deploy, so tell the user before step 4, and expect that build in step 6.
Done when the listing from step 3 shows exactly one active Apify webhook.
Push one commit to the branch the version builds from: the default branch, or the one after # in gitRepoUrl. An empty commit is enough:
git commit --allow-empty -m "Trigger build to test the build webhook"
git pushThen check all four:
push delivery with a 2xx status.Cloned commit ID equal to the pushed commit.taggedBuilds.<buildTag> points at that build.Done when all four hold. A failed check sends you back to the step for its link: the first two to the trigger link, the last two to the clone link.
Close by telling the user that a Build Actor webhook carries the API token they created for it: when that token is rotated, deleted or expires, pushes stop building without any notice, and the cure is step 5 again.
apify/agent-skills
0055082
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.