Skip to content

docs: rewrite GitHub integration page as step-by-step tutorial#2512

Open
marcel-rbro wants to merge 1 commit intomasterfrom
docs/github-integration-tutorial
Open

docs: rewrite GitHub integration page as step-by-step tutorial#2512
marcel-rbro wants to merge 1 commit intomasterfrom
docs/github-integration-tutorial

Conversation

@marcel-rbro
Copy link
Copy Markdown
Contributor

@marcel-rbro marcel-rbro commented May 7, 2026

Closes #2492

Summary

Rewrites sources/platform/integrations/programming/github.md:

  • Restructured as Prerequisites → Create an Actor from a GitHub repository (Steps 1-3) → Build automatically on every push → Create a GitHub issue when an Actor run fails (Steps 1-4) → Resources.
  • Updated the new-Actor walkthrough to match the current Apify Console UI ("Let's build a new Actor!" page, with GitHub listed directly under Link a Git repository - no intermediate provider modal).
  • Replaced the bare YouTube embed for the failure-issue flow with a written tutorial: generate a fine-grained GitHub PAT, add an ACTOR.RUN.FAILED HTTP webhook on the Actor, set the headers/payload templates to call POST /repos/{owner}/{repo}/issues, save and test. Kept the original video as a "Video walkthrough" subsection.
  • Refreshed two screenshots: apify-git-repository.png (the new-Actor page) and integrations-tab.png (the Add integration page; this image is also reused by slack.md and webhooks/index.md).
  • Removed the now-unused apify-git-provider-select.png (the provider-picker modal no longer exists).
  • Adopted the current intro convention (plain prose + <ThirdPartyDisclaimer />, no bold one-liner or --- rule), matching recent integration pages (Pipedream, Snowflake, Manus, viaSocket, x402).

Reviewer question

There's an inline MDX comment in the Build automatically on every push section asking whether the native "Link a Git repository" flow already wires up auto-builds (the panel's helper text suggests it does). If so, the manual GitHub webhook recipe currently in that section is the legacy path - please confirm and let me know whether to keep it as-is, replace it with a one-line note, or keep both with a clarifying intro.

Test plan

  • pnpm lint:md passes for the changed file
  • vale "sources/platform/integrations/programming/github.md" reports 0 errors
  • All cross-link slugs verified to exist (/platform/actors/development/deployment/continuous-integration, /platform/actors/development/deployment/source-types#private-repositories, /platform/integrations/webhooks/events, /platform/integrations/webhooks/actions)
  • pnpm build passes (no broken links, frontmatter valid)
  • Page renders correctly in dev server: prereqs, all numbered steps, admonitions, code blocks, and the embedded YouTube iframe
  • Slack and Webhooks pages still render the (replaced) integrations-tab.png correctly

🤖 Generated with Claude Code

…utorial

Restructures the GitHub integration page into prerequisites, a numbered
"Create an Actor from a GitHub repository" walkthrough that matches the
current "Let's build a new Actor!" UI, and a written tutorial for opening
a GitHub issue via Apify webhook + the GitHub REST API. Replaces the bare
YouTube embed and refreshes the new-Actor and Integrations-tab screenshots.

Closes #2492

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot added the t-docs Issues owned by technical writing team. label May 7, 2026
@marcel-rbro marcel-rbro changed the title docs(integrations): rewrite GitHub integration page as step-by-step tutorial docs: rewrite GitHub integration page as step-by-step tutorial May 7, 2026
@marcel-rbro marcel-rbro marked this pull request as ready for review May 7, 2026 09:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

t-docs Issues owned by technical writing team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve GitHub integration page

2 participants