Skip to content
This repository has been archived by the owner on Jun 8, 2023. It is now read-only.

IMPORTANT: No longer accepting new scripts to this package, create external packages instead #1113

Closed
tombell opened this issue Sep 4, 2013 · 23 comments

Comments

@tombell
Copy link
Contributor

tombell commented Sep 4, 2013

Please read https://github.com/github/hubot-scripts/blob/master/CONTRIBUTING.md if you're submitting a pull request for a new script, but basically new scripts aren't accepted.

We recommend hubot script packages now. Please check out the hubot-scripts organization for more details.

Once you've created a repository, you can file an issue against hubot-scripts/packages to have it forked to hubot-scripts, as well as to be added to the organization in order to maintain the fork.

See #1641 for current efforts to find extractions of scripts in this repository for npm packages

*Edit by @technicalpickles 2016-05-06: cross out out of date info, link to most recent deprecation efforts

@technicalpickles
Copy link
Contributor

Updated original issue to mention hubot-scripts/packages, the repository.

@tombell
Copy link
Contributor Author

tombell commented Sep 9, 2013

👍

rorito added a commit to rorito/hubot-imessage-deploy that referenced this issue Jun 15, 2016
moqada added a commit to moqada/kanmukun that referenced this issue Jul 17, 2016
roback added a commit to twingly/marvin that referenced this issue Aug 31, 2016
Getting deprecation notices for hubot-scripts, see
github/hubot-scripts#1113
xurizaemon added a commit to xurizaemon/bolts that referenced this issue Feb 24, 2017
@MrKeiKun
Copy link

MrKeiKun commented Mar 1, 2017

Hi how to load customize hubot-script now?
like before you can just put .coffee file inside myhubot/scripts/
then enable it via adding the file to hubot-scripts.json
But now, I tried doing it, it failed.

@patcon
Copy link
Contributor

patcon commented Mar 1, 2017

Hi @MrKeiKun! I'm not using hubot right now, but fwiw, github (and issue tracker) etiquette is to open a new issue for questions and comments not directly related to the issue topic (in this case: the org "No longer accepting new scripts to this package")

You should probably create a new one :) (ping me in the issue, and I'll try to help you troubleshoot)

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

No branches or pull requests

8 participants