This repository has been archived by the owner on Nov 4, 2022. It is now read-only.
When creating a remote repo with --new, do "git remote add origin" automatically #696
Labels
Comments
|
This sounds like a sensible default 👍 |
protoEvangelion
pushed a commit
to protoEvangelion/gh
that referenced
this issue
Nov 10, 2019
Create a new GitHub repository based on the name of the current directory & init with a README re node-gh#696
protoEvangelion
pushed a commit
to protoEvangelion/gh
that referenced
this issue
Nov 10, 2019
Create a new GitHub repository based on the name of the current directory & init with a README re node-gh#696
protoEvangelion
pushed a commit
that referenced
this issue
Nov 10, 2019
Create a new GitHub repository based on the name of the current directory & init with a README re #696
protoEvangelion
pushed a commit
that referenced
this issue
Nov 10, 2019
# [2.7.0](v2.6.1...v2.7.0) (2019-11-10) ### Features * **repo:** create new repo based on directory name and clone ([bed87f1](bed87f1)), closes [#696](#696)
|
🎉 This PR is included in version 2.7.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
@zevaverbach try |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the solution you'd like
A one-liner of (see #695)
gh --newthat creates a repository on GitHub, in this case named after the local repo's dirname, and adds the new repository as a remote calledorigin.The text was updated successfully, but these errors were encountered: