Enable close-stale-contributor-prs.yml workflow

[pakrym-oai]

Tested on #3036

[chatgpt-codex-connector]

💡 Codex Review

codex/.github/workflows/close-stale-contributor-prs.yml

Lines 51 to 70 in 2daf821

	let permission;
	try {
	const permissionResponse = await github.rest.repos.getCollaboratorPermissionLevel({
	owner,
	repo,
	username: pr.user.login,
	});
	permission = permissionResponse.data.permission;
	} catch (error) {
	if (error.status === 404) {
	core.info(`Author ${pr.user.login} is not a collaborator; skipping #${pr.number}`);
	continue;
	}
	throw error;
	}
	const hasContributorAccess = ["admin", "maintain", "write"].includes(permission);
	if (!hasContributorAccess) {
	core.info(`Author ${pr.user.login} has ${permission} access; skipping #${pr.number}`);
	continue;

Permission filter closes maintainers instead of contributors

Now that dryRun is false, the workflow will actually close the PRs selected by the filter below, but the filter only ever matches collaborators with admin/maintain/write access. Non-collaborator contributors hit the 404 in getCollaboratorPermissionLevel and are skipped, so the job never touches the very “contributor PRs” it is supposed to prune and instead auto-closes internal maintainer PRs after 14 idle days. That behavior was harmless while dry-run was true but becomes disruptive once the workflow runs for real.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".