Skip to content

[Sync] Update project files from source repository (cad9c92) - #221

Merged
mrz1836 merged 1 commit into
masterfrom
chore/sync-files-postmark-20261020-212006-cad9c92
Oct 20, 2026
Merged

mrz1836 merged 1 commit into
masterfrom
chore/sync-files-postmark-20261020-212006-cad9c92

Conversation

@mrz1836

@mrz1836 mrz1836 commented Oct 20, 2026

Copy link
Copy Markdown
Owner

What Changed

  • GOVULNCHECK_GO_VERSION: 1.27.2 → 1.27.3 (.github/env/00-core.env)
  • The pull-request-management.yml workflow now also triggers on the synchronize event for same-repo PRs, so the "🔧 PR Management (Same Repo)" job runs on every new head commit.
  • On synchronize runs, the label and default-assignee steps are skipped, and the job summary reports "None: new commits only". Concurrency for these runs uses a separate -push group, so a push right after a PR opens cannot cancel the run that labels it.
  • Comments in the workflow header, trigger configuration, and concurrency sections were rewritten to explain the new behavior. Fork PR handling through the workflow_run path is unchanged and still fires only on opened, reopened, ready_for_review, or closed.

Why It Was Necessary

  • A check run belongs to a single commit. If a ruleset requires the "PR Management (Same Repo)" check, any PR pushed to after opening would never get that check on its new head, which blocks the merge.
  • Running the job on synchronize without re-applying labels or the assignee reports the check on each head commit. Maintainers can still override auto-applied labels without the workflow undoing their changes.

Testing Performed

  • Reviewed the diff to confirm the synchronize guards on the label and assignee steps and the new summary branch.
  • Confirmed the concurrency expression appends -push only when the action is synchronize, so those runs are grouped separately from opened/reopened/ready_for_review/closed runs.
  • Behavior is best validated by pushing a commit to an open same-repo PR and checking that the check appears on the new head with no label or assignee changes.

Impact / Risk

  • Risk: Low. The new trigger runs a mostly no-op job on each push, adding a small amount of CI usage per PR update.
  • Fork PRs are not affected. Their pull_request runs skip the same-repo job, which satisfies a required check, and the fork path still uses workflow_run.
  • No breaking changes. Existing behavior for opened, reopened, ready_for_review, and closed events is unchanged.

@mrz1836 mrz1836 self-assigned this Oct 20, 2026
@mrz1836 mrz1836 added automated-sync Automated sync PR, e.g. from a fork or external repo automerge Label to automatically merge pull requests that meet all required conditions chore Simple dependency updates or version bumps labels Oct 20, 2026
@github-actions github-actions Bot added update General updates size/S Small change (11-50 lines) labels Oct 20, 2026
@mrz1836
mrz1836 merged commit 3b5c764 into master Oct 20, 2026
36 checks passed
@mrz1836
mrz1836 deleted the chore/sync-files-postmark-20261020-212006-cad9c92 branch October 20, 2026 21:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated-sync Automated sync PR, e.g. from a fork or external repo automerge Label to automatically merge pull requests that meet all required conditions chore Simple dependency updates or version bumps size/S Small change (11-50 lines) update General updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

⌂ 换网址