Skip to content

ci(sync-upstream): auto-resolve pr.yml by keeping fork version - #12

Merged
dogmar merged 3 commits into
mainfrom
claude/fix-upstream-sync-conflict-P3bzT
May 21, 2026
Merged

dogmar merged 3 commits into
mainfrom
claude/fix-upstream-sync-conflict-P3bzT

Conversation

@dogmar

@dogmar dogmar commented May 14, 2026

Copy link
Copy Markdown
Collaborator

Summary

The v0.21.1 upstream sync run failed with:

##[error]Unable to auto-resolve all conflicts. Manual intervention required:
.github/workflows/pr.yml

The fork has intentionally simplified .github/workflows/pr.yml:

  • No NX_CLOUD_ACCESS_TOKEN env (fork has no NX Cloud access)
  • No nx-set-shas step / fetch-depth: 0 (fork uses test:ci, not test:pr)
  • No preview job (fork doesn't run pkg-pr-new previews)

Because both sides touched this file in the v0.21.1 sync, git produced a content conflict and the auto-resolver had no rule for it. The same conflict will recur on every future upstream change to pr.yml.

This PR adds an auto-resolution rule that keeps the fork's version (git checkout --ours) — analogous to the existing rule for .github/workflows/release.yml, which is also fork-divergent.

If upstream introduces a pr.yml improvement the fork wants (e.g. action SHA pinning), the maintainer can cherry-pick it manually.

Test plan

  • Reproduced the v0.21.1 conflict locally by merging upstream/main into origin/main
  • Verified the new rule resolves .github/workflows/pr.yml cleanly (git checkout --ours + git add) and that release.yml still resolves
  • Confirmed git diff --name-only --diff-filter=U returns empty after applying both rules
  • Confirmed the resulting pr.yml on the merge branch matches the fork's simplified version
  • Next upstream sync run completes without manual intervention

https://claude.ai/code/session_01QaapKgU28S1T5TH2ffsay2


Generated by Claude Code

The fork has intentionally simplified .github/workflows/pr.yml (no NX
Cloud, no nx-set-shas, no preview job, uses test:ci instead of test:pr),
so any upstream change to that file conflicts with our customizations.
The v0.21.1 sync failed for this reason.

Add a rule to keep the fork's version on conflict, alongside the existing
rules for release.yml, changelogs, and example package.json files.
@autofix-troubleshooter

Copy link
Copy Markdown

Hi! I'm the autofix logoautofix.ci troubleshooter bot.

It looks like you correctly set up a CI job that uses the autofix.ci GitHub Action, but the autofix.ci GitHub App has not been installed for this repository. This means that autofix.ci unfortunately does not have the permissions to fix this pull request. If you are the repository owner, please install the app and then restart the CI workflow! 😃

@dogmar
dogmar marked this pull request as ready for review May 21, 2026 16:34
@dogmar
dogmar merged commit d080b2b into main May 21, 2026
3 checks passed
@dogmar
dogmar deleted the claude/fix-upstream-sync-conflict-P3bzT branch May 28, 2026 23:05
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.

2 participants