CircleCI workflows consistently erring for some exported PRs with permission issues

[janeyx99]

For some exported PRs, such as this one: #66431, the IOS circleci jobs along with the docker build jobs are all failing to run due to what seems like permissions issues.

The docker build jobs fail with:
Unable to locate credentials. You can configure credentials by running "aws configure".
See https://app.circleci.com/pipelines/github/jerryzh168/pytorch/3301/workflows/6b18045d-9dfa-42c5-9381-3d168fee47fe/jobs/24154

The ios jobs fail due to:
This build was not run because we couldn't find the "org-member" context
See https://circleci.com/gh/jerryzh168/pytorch/24159?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link

The binary job says that the machine size is not appropriate.
See https://circleci.com/gh/jerryzh168/pytorch/24153?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link

Most of Jerry's exported PRs have this sort of error:
https://github.com/pytorch/pytorch/pulls/jerryzh168

Speculation:
This could be due to Jerry's PRs not being provisioned as Jerry doesn't belong to the pytorch team and the combination that the PR was exported from internal pytorch.

cc @seemethere @malfet @pytorch/pytorch-dev-infra

[seemethere]

I think the last time we ran into this is because the actual jobs aren't running on pytorch/pytorch but rather your fork jerryzh168/pytorch, you can even see this in the URLs for the build that are linked in this original issue:

circleci.com/gh/jerryzh168/pytorch/24159?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link

I'm not entirely sure why this is actually the case so I'd recommend filing an issue with circleci support here: https://support.circleci.com/hc/en-us/requests/new

[malfet]

I think the last time we ran into this is because the actual jobs aren't running on pytorch/pytorch but rather your fork jerryzh168/pytorch, you can even see this in the URLs for the build that are linked in this original issue:

circleci.com/gh/jerryzh168/pytorch/24159?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link

Almost all of my PRs are exactly like that (for example see #66433 ), but I'm not running into aws not configured issue

[seemethere]

I think the last time we ran into this is because the actual jobs aren't running on pytorch/pytorch but rather your fork jerryzh168/pytorch, you can even see this in the URLs for the build that are linked in this original issue:

circleci.com/gh/jerryzh168/pytorch/24159?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link

Almost all of my PRs are exactly like that (for example see #66433 ), but I'm not running into aws not configured issue

Quick pass through on that particular PR shows links that look like:

app.circleci.com/pipelines/github/pytorch/pytorch/392702/workflows/c6cf39d8-acb1-4a4a-8f86-e9b3cf5a3df0/jobs/16411101

https://app.circleci.com/pipelines/github/pytorch/pytorch/392702/workflows/c6cf39d8-acb1-4a4a-8f86-e9b3cf5a3df0/jobs/16411101

[seemethere]

@jerryzh168 Can you go to https://circleci.com/gh/jerryzh168/pytorch/edit and unfollow that particular project?

I think that should resolve your issue.

[seemethere]

Closing since @jerry39213gh's problem is resolved