mj submit

[rueckstiess]

Splitting the original mj create (#4) into mj create and mj submit.

mj create only works locally but does not trigger any remote actions. mj submit does all the remote steps.

List of remote actions, left over from #4:

• [ ] gh repo --new {{name}} --organization mongodb-js --description "{{description}}" --homepage "https://github.com/mongodb-js/{{name}}" (create repo)
• [ ] git remote add origin git@github.com:mongodb-js/{{name}}.git
• [ ] travisjs encrypt SAUCE_USERNAME=mongodb-js -r mongodb-js/{{name}} --add;
• [ ] travisjs encrypt SAUCE_ACCESS_KEY=<how to get sauce api key?!?!?!> -r mongodb-js/{{name}} --add;
• [ ] travisjs hook (syncs + adds repo)
• [ ] git push origin master
• [ ] wercker/travis + npm version patch publish hook?
• [ ] incorporate other steps needed for semantic-release

[imlucas]

per note in #4, strongly strongly disagree. all this is doing is creating the remote properly + wiring travis.

[imlucas]

Actually I take it all back :p redact redact redact!

[rueckstiess]

o_O @imlucas

Happy to discuss either way :-)

But I just see the following happen. We blog about mj. Lots of people internally and externally want to try. They "mj create" something. Then they go away. We'll have hundreds of unfinished mongodb-js repos all with empty or dead code.

[imlucas]

@rueckstiess ja you're totally right. always some fixing up to do before you want to push to remote. submit also a good point to inject announcing the module to the rest of the org.