docs: rewrite GitHub integration page as step-by-step tutorial#2512
Open
marcel-rbro wants to merge 1 commit intomasterfrom
Open
docs: rewrite GitHub integration page as step-by-step tutorial#2512marcel-rbro wants to merge 1 commit intomasterfrom
marcel-rbro wants to merge 1 commit intomasterfrom
Conversation
…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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #2492
Summary
Rewrites
sources/platform/integrations/programming/github.md:ACTOR.RUN.FAILEDHTTP webhook on the Actor, set the headers/payload templates to callPOST /repos/{owner}/{repo}/issues, save and test. Kept the original video as a "Video walkthrough" subsection.apify-git-repository.png(the new-Actor page) andintegrations-tab.png(the Add integration page; this image is also reused byslack.mdandwebhooks/index.md).apify-git-provider-select.png(the provider-picker modal no longer exists).<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:mdpasses for the changed filevale "sources/platform/integrations/programming/github.md"reports 0 errors/platform/actors/development/deployment/continuous-integration,/platform/actors/development/deployment/source-types#private-repositories,/platform/integrations/webhooks/events,/platform/integrations/webhooks/actions)pnpm buildpasses (no broken links, frontmatter valid)integrations-tab.pngcorrectly🤖 Generated with Claude Code