Skip to content

chore(ci): remove inherited PR_Branch_Check workflow (misfires on our fork)#2

Open
asachs01 wants to merge 1 commit into
masterfrom
chore/remove-fork-pr-autoclose
Open

chore(ci): remove inherited PR_Branch_Check workflow (misfires on our fork)#2
asachs01 wants to merge 1 commit into
masterfrom
chore/remove-fork-pr-autoclose

Conversation

@asachs01

Copy link
Copy Markdown
Member

Upstream's PR_Branch_Check.yml (pull_request_target) auto-closes fork PRs targeting main/master and steers them to dev. Because wyre-technology/CIPP-API is itself a fork, head.repo.fork is permanently true for every same-repo PR — so it auto-closed every PR to master (structural dead-end for internal contributions; caught when a docs README PR closed within seconds). Already disabled manually; this removes the file. WYRE develops on master here (default=master, no dev branch, not an external-contributor funnel). Reversible via git history if the dev-branch convention is ever wanted.

… fork)

Upstream KelvinTegelaar/CIPP-API uses this pull_request_target workflow to
auto-close external-contributor fork PRs and steer them to dev. But
wyre-technology/CIPP-API is itself a fork, so head.repo.fork is permanently
true for every same-repo PR — it auto-closed ALL PRs to master (a structural
dead-end for internal contributions). Already disabled manually; this removes
the file. WYRE develops on master here (default=master, no dev branch).
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