Skip to content

fix(ci): trigger Coding CI on main branch instead of stale master#149

Merged
jeff-r2026 merged 1 commit into
mainfrom
fix/coding-ci-main-branch-gh
Jul 3, 2026
Merged

fix(ci): trigger Coding CI on main branch instead of stale master#149
jeff-r2026 merged 1 commit into
mainfrom
fix/coding-ci-main-branch-gh

Conversation

@jeff-r2026

Copy link
Copy Markdown
Collaborator

Problem

The TGit (git.woa.com) mirror's default branch was renamed from master to main (master was deleted), but .coding-ci.yaml still hardcodes master in two places:

trigger:
  branches:
    include:
    - master        # push-triggered validate(lint+test)/build/e2e
mr:
  branches:
    include:
    - master        # MR-triggered checks

Since the rename, pushes and MRs targeting main on TGit no longer trigger the validate/build/e2e pipeline. Tag-triggered publish (e.g. the v0.17.0 release) is unaffected since it matches an independent tags.include pattern.

This file has no effect on GitHub CI (which uses .github/workflows/), but it's kept in sync via the periodic TGit↔GitHub sync process, so fixing it here prevents it from being reverted back to master next time TGit syncs from main.

Change

Replace master with main in trigger.branches.include and mr.branches.include.

Made with Cursor

工蜂(TGit)侧的默认分支已从 master 改为 main(master 已删除),但
.coding-ci.yaml 的 trigger.branches.include 和 mr.branches.include
仍写死为 master,导致 push main / MR 到 main 均不再触发 validate
(lint+test)/build/e2e 检查。

Co-authored-by: Cursor <cursoragent@cursor.com>
@jeff-r2026 jeff-r2026 merged commit 77daf15 into main Jul 3, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant