70177c72c5
Link in the README to all the places where issues can be found and add a minimal contribution guide. <!--start release-notes-assistant--> <!--URL:https://code.forgejo.org/forgejo/runner--> - other - [PR](https://code.forgejo.org/forgejo/runner/pulls/1495): <!--number 1495 --><!--line 0 --><!--description Y2hvcmU6IGFkZCBpc3N1ZXMgdG8gUkVBRE1FLCBtaW5pbWFsIGNvbnRyaWJ1dGlvbiBndWlkZQ==-->chore: add issues to README, minimal contribution guide<!--description--> <!--end release-notes-assistant--> Reviewed-on: https://code.forgejo.org/forgejo/runner/pulls/1495 Reviewed-by: Mathieu Fenniak <mfenniak@noreply.code.forgejo.org>
1.2 KiB
Contributing to Forgejo Runner
Thank you for wanting to make Forgejo Runner better!
Before Sending a PR
Before sending a PR, please read the Forgejo Contributor Guide and the AI Agreement.
Forgejo Actions is a complex beast with intricate compatibility requirements. Some features are also out of scope. Therefore, we recommend proposing your changes in an issue or feature request before coding up a solution. Please note that we do not accept new features without having them discussed beforehand. New features also have a lower priority than bug fixes.
PRs do not need to be perfect.
What to Expect
Be ready for lengthy feedback. It is common that enhancements or even bug fixes need multiple iterations until they are ready. Sometimes, we even realize during review that a particular feature or approach is not the right solution.
We Are Here to Help
Do not hesitate to ask for help or advice. You can do so in an issue, a PR, or in the developer room on Matrix.