Plugin Template

This repository serves as a template that can be used to quickly get a plugin published to PyPI as well as establish a consistent development environment with the rest of Moe.

By following the instructions of this template repository, you will setup a plugin that has the following features:

1. Automatic release process initiated by a manual trigger.

   • Changelog generation as well as releasing to PyPI and github are all initiated by running the Create Release PR github action. Once run, it will create a pull request for the new release which will allow you to edit the generated changelog prior to rebasing the PR onto the main branch. Once rebased into main, the Release github action will automatically run, publishing your new release.

   Important

   The automatic changelog generation is dependent on you adhering to the specific commit conventions of Moe.

2. Plugin documentation hosted on Read the Docs.
   • As well as creating a consistent documentation interface with the rest of Moe, the main benefit of this is to use the auto-documentation feature of Sphinx for any API functions your plugin may provide.
3. Project and dependency management using Poetry.
4. A CI suite that will run tests, lint your code, and build the documentation of any PR.

Instructions

1. Create a new repository from this template repository.
   • Name your repository moe_{plugin name}. This will be the name of your package on PyPI as well.
2. Edit pyproject.toml.
   • Edit any information in the tool.poetry and tool.poetry.plugins."moe.plugins" sections.
3. Edit github scripts and files.
   • .github/ISSUE TEMPLATE contains default issue templates that Moe uses. At a minimum, you need to change the url in config.yml to link to your repository's discussions.
     • You must also enable 'Discussions' in your repository settings in order for the referenced link to work.
   • Edit the SLUG constant in .github/scripts/prep_release.py to be your repository.

4. Setup documentation on Read the Docs.

   Note

   This step is optional if you are not providing any new API functions with your plugin. In that case, you may remove the docs directory as well as the .readthedocs.yml file.

   • Edit docs/conf.py project information.
   • Import your repository into Read the Docs.
     • This is the site used to host your documentation.
   • Configure your project to build docs on pull requests.
     • Readthedocs project -> Admin -> Settings
       • Check the box in the settings to build pull requests.
   • Edit the project-slug in .github/workflows/preview_docs.yml to be your readthedocs project slug.
5. Edit plugin information.
   • Edit the repository "About" section on github
     • Ensure to add your documentation link to the Website section.
   • Edit README.rst
   • Edit docs/index.rst
6. Setup PyPI publishing.
   • In your PyPI account, add the release.yml github action as a trusted publisher.
7. Edit repository "About" information.
   • Ensure to add your documentation link to the Website section.
8. Optional: Setup code coverage reports in pull requests.
   • Connect the repository with Codecov.
   • Add the CODECOV_TOKEN secret to the repository.
9. Once finished, commit your changes and create a v0.1.0 tag. Then, push your changes with the new tag.

Contributing

If you find any steps missing, confusing, outdated, etc, please don't hesitate to create an issue, discussion, or PR. I'd like this repository to be a central truth for any shared project files such as linter settings, CI scripts, test helper functions, and anything else contained here.