"Create a new PR" doesn't target the correct specified GitHub repo

[beafialho]

When I create a new PR to add a new theme to the repo, I would expect it to end up on https://github.com/Automattic/themes/, but the PR is opened from a fork of this repo https://github.com/beafialho/themes instead.

More context

[brandonpayton]

Based on permissions, it looks like this should be working for @beafialho, but perhaps we are encountering an error and pushing to a fork as a fallback here:

wordpress-playground/packages/playground/website/src/github/github-export-form/form.tsx

Lines 933 to 942 in a7004a5

	if (
	e.status === 403 &&
	e.message?.includes(
	'organization has enabled OAuth App access restrictions'
	) &&
	!shouldFork
	) {
	return await pushToGithub(octokit, {
	...options,
	shouldFork: true,

[adamziel]

GitHub permissions are weird. Sometimes you are a repo admin, but the organization restricted what you can do via different types of auth tokens – like the OAuth token we use here. Assuming organization restrictions are the problem here, here's what would help:

• A clear feedback for the user whenever we encounter a permissions issue and need to fall back to a fork
• A way to provide a personal access token that doesn't have the same restrictions

[adamziel]

Since this issue is a blocker for GitHub automations leaving comments with PR preview links in the Automattic/themes repo (since the pull_request: trigger won't run for forks), I left this comment and added the other issue to the board:

@mikachan would there be anything wrong with using the pull_request_target: trigger instead of pull_request: in the preview-theme.yml workflow? This would make it work for PRs from forks.