You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CircleCI is offering a new way of working with GitHub repos, using the GitHub App instead of the GitHub OAuth App. This, however, includes some changes which are incompatible with this orb.
The incompatibilities I've been able to find:
CIRCLE_REPOSITORY_URL environment variable is no longer set, but is available through the pipeline parameter << pipeline.project.git_url >>
API calls using ${VCS_TYPE}/${CIRCLE_PROJECT_USERNAME}/${CIRCLE_PROJECT_REPONAME} are invalid:
The VCS_TYPE for such projects must be set to circleci
CIRCLE_PROJECT_USERNAME and CIRCLE_PROJECT_REPONAME resolve to human-readable values, but the API expects the arbitrary string id values that are instead available in the CIRCLE_ORGANIZATION_ID and CIRCLE_PROJECT_ID variables, respectively
The text was updated successfully, but these errors were encountered:
Would also love to see this feature, as new CircleCI orgs are automatically created with the Github App integration instead of Github Oauth. We're testing out this orb, as we need a way to disable concurrent workflows from the same branch, and are getting the error
ERROR: Server returned error code: 404
{
"message" : "Project not found"
}
Which I assume is in the way the API call differs, as @maciejb mentioned above.
CircleCI is offering a new way of working with GitHub repos, using the GitHub App instead of the GitHub OAuth App. This, however, includes some changes which are incompatible with this orb.
The incompatibilities I've been able to find:
CIRCLE_REPOSITORY_URL
environment variable is no longer set, but is available through the pipeline parameter<< pipeline.project.git_url >>
${VCS_TYPE}/${CIRCLE_PROJECT_USERNAME}/${CIRCLE_PROJECT_REPONAME}
are invalid:VCS_TYPE
for such projects must be set tocircleci
CIRCLE_PROJECT_USERNAME
andCIRCLE_PROJECT_REPONAME
resolve to human-readable values, but the API expects the arbitrary string id values that are instead available in theCIRCLE_ORGANIZATION_ID
andCIRCLE_PROJECT_ID
variables, respectivelyThe text was updated successfully, but these errors were encountered: