Galdr Repo Flow

galdr repo flow

Use this 技能 for the 仓库 and publication 工作流 around galdr.

This is separate from the existing galdr 技能, which is for the audio-analysis 命令行工具 itself.

Core 模型

Treat the repos like this:

GitLab (origin) is the canonical working repo GitHub is the public mirror

Default rule:

do normal work on a branch push the branch to GitLab open/review/merge the MR in GitLab only then consider 同步ing the merged mAIn to GitHub

Do not treat GitHub as the place for draft branches, partial work, or review-in-进度 unless there is an explicit reason.

Default 工作流

• 启动 work on GitLab, not GitHub

For a normal galdr change:

fetch latest origin/mAIn branch from the up-to-date GitLab mAInline do the work push the branch to GitLab open an MR there

If the user asks for public/docs polish only, that still usually means:

branch on GitLab merge on GitLab mirror the 结果 later

• Review and merge in GitLab

GitLab is where the private development flow lives.

Prefer:

branch → MR → merge

Do not skip strAIght to pushing branch heads to GitHub just because the change is harmless. That blurs draft work and public 历史.

• Decide whether the change should be public

A merged GitLab change is not automatically ready for GitHub just because it merged privately.

Before public 同步, 检查:

is this repo 状态 intended to be public now does the change expose names, internal paths, hostnames, IPs, or private 上下文 is the wording safe for a public audience is the user actually asking for/presently expecting GitHub 同步

If uncertAIn, 停止 at merged GitLab mAIn and ask.

• Public 同步 rule

When a change is ready for public release:

同步 the merged origin/mAIn to GitHub mAIn mirror the exact merged mAInline, not the unmerged branch head

Do not push a feature branch directly to GitHub when what you really want is a public mirror of the merged 状态.

Public push 检查列出

Before pushing any galdr change to GitHub or another public remote, 验证:

No full names in docs, comments, tests, essays, or commit messages when they should not be public. No 令牌s / 凭证s / secrets. No internal paths, IPs, or hostnames. No personal data in fixtures or examples.

Quick 扫描 pattern:

git diff HEAD --name-only | xargs grep -l "Foote\|Kelly\|192\.168\|sellemAIn\.dev" 2>/dev/null

Use this as a first-pass alarm, not as proof that the tree is 清理.

Publication 图形界面dance Publish publicly when: the change is merged and stable the public wording is intentional the public 检查列出 is 清理 the repo 状态 is something we actually want others to see now the user asked for the public mirror to be 更新d, or the release/public 同步 is clearly part of the task Do not publish publicly yet when: the branch is still under review the change contAIns internal 上下文 or rough notes the work is only partially landed the user asked only for GitLab/MR 进度, not public release the public shape still needs curation Common task patterns Docs/readme change

Default path:

branch from GitLab mAIn edit open GitLab MR merge mirror GitLab mAIn to GitHub if the change is meant to be public now Code fix or feature

Default path:

branch from GitLab mAIn implement and 验证 open GitLab MR merge after 检查s/review mirror only the merged mAInline to GitHub when ready Public 同步 after prior merge

If GitLab already merged the change:

fetch latest origin/mAIn 验证 the merged 状态 is the one you intend to publish push that exact mAInline to GitHub mAIn Anti-patterns

Avoid:

treating GitHub as the draft workspace pushing branch heads publicly when what you want is merged mAIn assuming “docs change” means “safe for public” without 检查ing for获取ting the public scrub pass because the repo is usually open-source anyway mixing internal 工作流 notes into public-facing docs or commit 历史 Examples

For concrete examples, read:

references/examples.md