-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement new plugin for node-gh #8
Comments
Love it. I can imagine typing Interested in helping contribute? Happy to go over the simple patterns involved in making a plugin, and equally happy to split up the work. |
yeah, that sounds good to me. Maybe we could split the work between you working on |
went ahead and created a new repo to house the plugin here and added you as a collaborate. the initial skeleton is there, just need to fill in the commands. |
the best way to get started is to do the following:
you can then write your command and test using |
thanks, I'll poke around this repo to get started and see how I make out. |
You might have to do a |
I am having trouble getting the
I am confused on what to do next. How do I get the Output from npm list:
|
So, you're developing it locally. You've got a couple options. You can reference your modified version of the code directly, You probably just want to npm link it. |
Btw, the best way to get all of meta on your system is not with git, it's with meta itself.
meta git clone will get all the plugin repos as well. |
Actually this may do it for you entirely:
After that you should have all of meta's repos, they should all be installed and linked, and meta, itself, should be linked for global usage. |
I get that I want to use meta to get everything initialized, but I feel like I have a chicken and egg situation. ie. I want to run this command to bootstrap everything but I don't yet have a
|
It's ok to do it with meta installed globally before. You'll just end up in a situation where your global meta bin will be replaced with a symlink to your local install's bin. When you're done developing locally, you just May need to npm unlink in the meta dir first. |
nice, all good! 👍
|
ah! yup. sorry. didn't mean to push that one. thanks! |
This is done over here: https://www.npmjs.com/package/meta-gh |
Added in commit 8b34186 |
Hi, As a user trying to install meta, I'm struggeling to get the meta commands to work. I get: |
Meta is a global command. `npm i -g meta`.
…On Wed, Mar 25, 2020 at 2:58 AM oscarpeterson ***@***.***> wrote:
Hi, As a user trying to install meta, I'm struggeling to get the meta
commands to work. I get:
"command not found: meta" - whenever I try to run something. What am I
missing? :)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEHOX7GSCYKYQTQN2BOC7LRJG2RNANCNFSM4DFJUVZQ>
.
|
Thanks for the reply. Yes I'm able to run 'npm i -g meta' and it seems to work. But when I'm for example trying to run 'meta' or 'meta git clone...' I get : "command not found: meta" |
You have something wrong with your node installation, and globally
installed modules are not found in your PATH variable. You'll have to
research that problem.
…On Wed, Mar 25, 2020 at 8:25 AM oscarpeterson ***@***.***> wrote:
Thanks for the reply. Yes I'm able to run 'npm i -g meta' and it seems to
work. But when I'm for example trying to run 'meta' or 'meta git clone...'
I get : "command not found: meta"
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEHOX3Y2SSHMXMJGXNHMO3RJIA4DANCNFSM4DFJUVZQ>
.
|
Thanks! I'll look into that. |
As a user, I would like to use meta commands that wrap the node-gh app.
The main use case is interacting with pull requests, mainly
list
,merge
, andrebase
.The text was updated successfully, but these errors were encountered: