Skip to content
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

Document finding and adding external scripts #901

Closed
technicalpickles opened this issue Mar 18, 2015 · 5 comments
Closed

Document finding and adding external scripts #901

technicalpickles opened this issue Mar 18, 2015 · 5 comments

Comments

@technicalpickles
Copy link
Member

I proposed this in hubot-archive/packages#60 (comment)

Basically, since we've been doing script packages, the example (or generated) package.json has the 'hubot-scripts' keyword. I already said that in the context of having a web accessible view. But it turns out, npm has a CLI way of searching packages, as well as seeing more info:

connor:examplebot technicalpickles$ npm search hubot-scripts pagerduty
NAME                   DESCRIPTION                                               AUTHOR            DATE       VERSION KEYWORDS                            
hubot-pager-me         PagerDuty integration for Hubot                           =technicalpickles 2014-12-16 2.0.2   hubot hubot-scripts pagerduty       
hubot-pagerduty-github PagerDuty Integration for checking who's on call, making… =patcon           2014-04-24 0.1.0   hubot hubot-scripts pagerduty alerts
npm home hubot-pager-me

At that point, npm opens a browser window for the homepage, where the user can figure out the next steps for installing.

We can add that to the hubot docs, along with things like how to update hubot and scripts.

I think docs/index.md would be a good place for this, but open to ideas.

@jglovier
Copy link

@technicalpickles so if I'm following this correctly, it's just a matter of adding the instructions to the docs, then, yes?

@technicalpickles
Copy link
Member Author

@jglovier that's it exactly. It's mostly finding the right place so it flows, and is easy to find.

@jglovier
Copy link

🤘

Yeah index feels legit - at least for now.

@geoffreyanderson
Copy link
Contributor

Since #956 was merged, this is probably good to close @technicalpickles @jglovier @bkeepers?

@technicalpickles
Copy link
Member Author

@geoffreyanderson Yep, thanks for the reminder!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants