Repository navigation
[Sync] Update project files from source repository (cad9c92) - #221
Merged
mrz1836 merged 1 commit intoOct 20, 2026
Merged
Conversation
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
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.
What Changed
GOVULNCHECK_GO_VERSION:1.27.2→1.27.3(.github/env/00-core.env)pull-request-management.ymlworkflow now also triggers on thesynchronizeevent for same-repo PRs, so the "🔧 PR Management (Same Repo)" job runs on every new head commit.synchronizeruns, the label and default-assignee steps are skipped, and the job summary reports "None: new commits only". Concurrency for these runs uses a separate-pushgroup, so a push right after a PR opens cannot cancel the run that labels it.workflow_runpath is unchanged and still fires only on opened, reopened, ready_for_review, or closed.Why It Was Necessary
synchronizewithout 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
synchronizeguards on the label and assignee steps and the new summary branch.-pushonly when the action issynchronize, so those runs are grouped separately from opened/reopened/ready_for_review/closed runs.Impact / Risk
pull_requestruns skip the same-repo job, which satisfies a required check, and the fork path still usesworkflow_run.