GPT-5 finding
Comment implies commit hooks will reject conflict markers; misleading in CI context
lowdocs-gaphigh
- .github/workflows/sync-upstream.yml:59-61
In GitHub Actions runners, local Git hooks are not installed by default, and committing files with conflict markers is technically allowed after staging. The comment suggests hooks would reject such commits, which is not generally true in this CI environment and may mislead maintainers about the necessity of `--no-verify`.
Recommendation
Clarify the comment to state that `--no-verify` is used to bypass any potential local hooks if present, though CI typically has none. Consider removing `--no-verify` if no hooks are enforced in this repository, or explicitly document when it is required.