Thanks for reading this contribution guide! 😊
Note
This guide is currently still work in progress. Expect changes, especially clarifications to appear here in the future.
Tip
Anything unclear? Feel free to ask @jxn-30 for clarification!
Some steps are
- clone
- run
yarn install
- develop and test
- run
yarn run lint:fix
andyarn run prettier:write
to lint and format. See section Pre-Commit- fix any warnings and errors reported by ESLint
- commit using Conventional Commits. See section Commit messages for more info.
- Create a Pull-Request
The package.json
of Better-Moodle includes scripts for formatting (prettier:write
) and linting (lint:fix
), the Better-Moodle repository also includes an up-to-date release of Yarn package manager.
Please run both scripts with yarn (yarn run lint:fix
and yarn run prettier:write
) before committing and also fix any warnings and issues reported by ESLint.
Better-Moodle uses Conventional Commits in its latest version, which is 1.0.0
at the time of writing.
This ensures that Release Please can generate the changelog.
Release Please introduces some additional features such as commit messages that allow to document multiple changes within a single commit.
Please review the docs of Release Please for more information on how to use them.
The use of the Release-As
-Directive of Release Please is discouraged for use in Better-Moodle main repository.
Your Pull Request should have a meaningful title as well as a content describing the changes introduced by this PR. There currently is no Pull Request Template available for Better-Moodle.
Please do not manually edit the CHANGELOG.md
file as the Changelog is generated by Release Please
There currently are no automated tests available. Please always make sure that Better-Moodle works on latest 3 to 4 versions of common browsers (Firefox and chromium based). You may also want to test Better-Moodle on mobile devices if possible.