Contributing
Last updated
Was this helpful?
Last updated
Was this helpful?
Mechanic's is a central resource for the entire community, and is continually enriched through contributions, via pull requests .
You've created a custom task, and you want to share it with the world! This brings us so much joy, and this is what the Mechanic project and this community are all about. If you get stuck along the way, please hop onto the , and we'll be glad to help.
We follow the same process any open-source project does when it comes to code management and code contributions. One bonus of contributing to the Mechanic task library is that once you learn the process here, you'll know how to contribute to open-source projects going forward.
You'll the task library .
Forking means taking a copy of our repository, so that you can make your changes and additions.
Make your changes in your forked repository.
Make a , which will trigger a review of your proposed changes and the merging of them into the main repository, making your task available to everyone using the app.
You'll need a GitHub account, you can signup for one .
Visit the and fork it as shown below. You'll make your changes to this copy of the repository.
The task library is made up of the and the supporting documentation. In these next few steps, you'll ensure you can build the , so that you can complete this step when you are ready to submit your contribution.
Building the docs requires nodejs and npm. You can install them from here:
While in the project directory, run the following commands to build the docs:
Now that you can build the docs you are ready to !
Your task documentation, options, subscriptions, code, are done in Mechanic. If you choose to use an external editor that's great, you still need to transfer it into Mechanic, so that you can export the task in the JSON format you need for the library. Importing/Exporting tasks from Mechanic is covered .
If you're changing an existing task you the JSON, and replace the contents of the task/task_file_name.json and then run the commands npm run build and npm run test.
If you are contributing a new task, you'll the JSON from Mechanic, and save the JSON file in the tasks/directory of your forked repository, named with an appropriate handle for the task. (For example, a task named "Hide out-of-stock products" should have its JSON export stored in "tasks/hide-out-of-stock-products.json".) And, then you'll execute the commands:
npm run build and npm run test.
If all goes well with the build, you'll see your task listed in the automatically created documentation in docs/README.md
You're now ready to make your pull request! Head over to and click New pull request, you should see the changes you committed to your fork, and you'll proceed with filling out the pull request form.
After you submit your first pull request, you will be required to read and accept . The will leave a comment, giving you a statement of agreement that you must paste into a comment of your own.
This process could sound confusing if you haven't done it before, but once you've done it once, it's simple and it is also pretty exciting to go through the process. The other bonus is, you'll be ready to submit a pull request to any open-source software project in the future. If you need help please out to us in the .
