This issue depends on:
This issue is related to:
The functionality in the contrib/ads-gh-repo script should be used as the basis for a new ads-github-repo program, which would have the long-term goal of providing mechanisms for those portions of the GitHub "Repositories" API that manipulate a single repository.
The current functionality will create a new GitHub repo for the authenticated user, and switch it's default branch name to a specified name. Currently the specified name is just 'whatever' (hard-coded in a program variable), but a non-sketch version would honor the new (since git 2.28, spring 2020) init.defaultBranch setting from the user's git configuration, or the name specified on the command line.
UPDATE (2020-10-05 22:06:39-04:00): For now we are going to implement a stand-alone ads-github-repo-create tool, since that is the shortest path to scratching the immediate itch. However, see also issue #51 for ideas about generalizing the approach for other single-repo operations.
This issue depends on:
This issue is related to:
The functionality in the contrib/ads-gh-repo script should be used as the basis for a new
ads-github-repoprogram, which would have the long-term goal of providing mechanisms for those portions of the GitHub "Repositories" API that manipulate a single repository.The current functionality will create a new GitHub repo for the authenticated user, and switch it's default branch name to a specified name. Currently the specified name is just 'whatever' (hard-coded in a program variable), but a non-sketch version would honor the new (since git 2.28, spring 2020)
init.defaultBranchsetting from the user's git configuration, or the name specified on the command line.UPDATE (2020-10-05 22:06:39-04:00): For now we are going to implement a stand-alone
ads-github-repo-createtool, since that is the shortest path to scratching the immediate itch. However, see also issue #51 for ideas about generalizing the approach for other single-repo operations.