[pr-staging-deploy]: multi-repo config, service naming, and webhook routing#442
Open
ArtemLazarchuk wants to merge 1 commit intodevelopmentfrom
Open
[pr-staging-deploy]: multi-repo config, service naming, and webhook routing#442ArtemLazarchuk wants to merge 1 commit intodevelopmentfrom
ArtemLazarchuk wants to merge 1 commit intodevelopmentfrom
Conversation
- Added StagingReposProvider to manage multiple repository configurations. - Updated services to utilize StagingRepoConfig for handling deployments across different repos. - Enhanced GitHubWebhookHandler to route events based on repo configuration. - Modified StagingDeployService to support dynamic service name generation based on repo keys. - Updated README to reflect changes in configuration and deployment behavior.
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
1 participant
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.
Summary
Extend PR Staging Deploy so one instance can manage staging for multiple GitHub repos, with clear Sliplane service names, reliable webhook routing, and docs-only / samples-only setups.
What changed
StagingReposProvider— loadsRepos[]from config; falls back to legacyGitHub:Owner/GitHub:Repo+Staging:*whenReposis empty.StagingRepoConfig/StagingComponentConfig— per-repo Docs and/or Samples (Dockerfile, context, clone URL).GitHubWebhookHandler— resolves the target repo from the webhook payload and ignores events for repos not listed in config.StagingDeployService— deploy/delete/redeploy keyed byStagingRepoConfig; single slug service names ({slug}-staging-docs-{PR},{slug}-staging-samples-{PR}) with configurableStaging:DeploymentKeyand legacy name parsing for existing services.PrStagingDeployCommentService— optional Docs/Samples lines in PR comments;GitHub:Tokenfallback ifGitHub:PrCommentTokenis unset.PrStagingDeployApp— table shows Repo, rows per repo × PR; Samples column hidden when no repo has Samples configured.README— secrets-first setup, multi-repo mention, service naming, webhook troubleshooting trimmed.Migration / ops
Repos[].2026-04-28.22.51.14.mov