Skip to main content

v2.81.1

Binaries and the merged-pull-request list are on the GitHub releases page.

A product repository can live in a personal account​

A blueprint names the repository's owner as one input, githuborg, whether that is an organization or someone's personal account. orun.repo/ensure@v1 always created through the organization endpoint, so a personal account failed in 01-scaffold with a bare GitHub answered 404 for /orgs/<owner>/repos: Not Found.

The action now asks GitHub what the owner is:

  • An organization is created in exactly as before.
  • A personal account is created in through POST /user/repos when the credential is that account's own. repoPrivate is respected.
  • A personal account the credential does not belong to (another user's token, or a GitHub App installation token) is refused with an error that names both accounts and the gh repo create <owner>/<name> --private command that creates it ahead of time. GitHub only creates a repository in a personal account for that account's own token, so orun no longer attempts it.

A repository that already exists is still found first and never re-created, so pre-creating it keeps working. The inOrg parameter is now consulted only when GitHub cannot say what kind of account the owner is.