teahubxyzandClaude Opus 5.5
745231844f
sync: secret names Gitea accepts (SYNC_GITHUB_KEY, SYNC_GITHUB_TOKEN) (#179) Gitea refuses secret names starting GITHUB_ or GITEA_, so the GitHub copy's deploy key is in SYNC_GITHUB_KEY. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017K4vyY3yUD3GsvoZaAtKkD
22 lines
924 B
JSON
22 lines
924 B
JSON
{
|
|
"_about": "Copies of repos on other forges, kept in step by .github/time/sync.py (the sync workflow). Each repo has one home (this forge) and every branch one writer: the `out` branches go from the home to each copy, fast-forward only; a copy's branches matching its `import` patterns come back to the home as PRs. `token` (https) or `ssh_key` (a deploy key, for ssh/git@ URLs; host keys pinned) names the secret that holds the credential, never the credential itself (Gitea refuses secret names starting GITHUB_ or GITEA_); a copy whose secret isn't set is skipped. A GitHub copy needs GitHub Actions turned off, since these workflows must only run here.",
|
|
"repos": [
|
|
{
|
|
"repo": "teahubxyz/time",
|
|
"out": [
|
|
"main"
|
|
],
|
|
"copies": [
|
|
{
|
|
"name": "github",
|
|
"url": "git@github.com:teahubxyz/time.git",
|
|
"ssh_key": "SYNC_GITHUB_KEY",
|
|
"import": [
|
|
"claude/*"
|
|
]
|
|
}
|
|
]
|
|
}
|
|
]
|
|
}
|