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
Right now, create requires the user be authenticated with GitHub to create a repository. An Octokit instance is created during runtime always. Which is reasonable and convenient for feature parity with create-typescript-app and the single place I personally always put my repositories on, GitHub...
But there are other authentication and repository hosts out there! At least:
Azure DevOps
GitLab
Theoretically others that people will want to ad hoc plug in on their own
Long-term, the create engine will need to be able to support that. I don't know yet what that will look like.
Bug Report Checklist
main
branch of the repository.Overview
Right now,
create
requires the user be authenticated with GitHub to create a repository. An Octokit instance is created during runtime always. Which is reasonable and convenient for feature parity with create-typescript-app and the single place I personally always put my repositories on, GitHub...But there are other authentication and repository hosts out there! At least:
Long-term, the
create
engine will need to be able to support that. I don't know yet what that will look like.Additional Info
It's not going to happen in milestone/2 Blocks Launch, and I'm not sure whether it'll even happen in milestone/3 Broad Launch. Marking as blocked for a while. But it definitely should happen.
This came in part out of talking with @johnnyreilly about the work he's been doing on his personal and corporate templates. https://johnnyreilly.com/npx-and-azure-artifacts-the-secret-cli-delivery-mechanism talks a good amount about Azure DevOps / Azure Artifacts hooks.
Co-authored-by: @johnnyreilly
The text was updated successfully, but these errors were encountered: