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
Adding initial CONTRIBUTING.md file #777
Conversation
Good call on this, really I should have had a CONTRIBUTING file here ages ago. Some minor questions; * I've been using the capitalisation `Skills` on all our documentation - as it denotes a certain importance to Skills. I'd like to do same here but thought it was really nitpicking to do so and wanted to check first. * Do we want to push people to list their Skill on the Skill Feedback topic on the Forum first before submitting here to make sure it works and the "tougher" testing that is done here is not wasted? Also, feel free to tell me to stop sticking my beak in; not my paddock any more! ;-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All sounds good to me. This is still your paddock too! :)
``` | ||
mycroft-msk submit <local-path-to-your-skill> | ||
``` | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might want to add something like:
Note: If you have two-factor authentication enabled for github, you will need to generate a [personal access token](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) and use the `-t` flag. E.g.
mycroft-msk -t submit <local-path-to-your-skill>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done!
Since there's not been any new comments on this one for the past five days, can we merge it as it stands now? |
Add a CONTRIBUTING guide.