Since the formality checks are now automated via the webhook, contributors
no longer need to manually go through a checklist. The bot will flag any
issues, request fixes, and apply a label indicating that requirements are
not met. Once all issues are resolved, the label is automatically removed.
This also benefits maintainers during review, as the previous manual
checklist could be skipped or filled with inaccurate information.
Remove the checklist items that are now automatically enforced and keep
only the ones that are not yet automated and still make sense to have.
Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
For PR template, minor fix to 'please read'
section, as symbol spacing was different
on GitHub website than on GitHub Desktop.
Added HTML comment with example on how
to complete the checklist using [x]. Added
examples to the 'tested on' section.
Added abbreviation explanation for PR to
better understand terminology, similar to
using S.O.B. For CONTRIBUTING.md,
bumped up release branch example, and
minor capitalisation fixes for PR.
Signed-off-by: Joshua Criss <owlsy@outlook.com.au>
As a new person to contributing on GitHub,
I noticed the Pull Request template missing
some important information that I would not
have known until I tried my first Pull Request,
such as the character limits and email
requirements. I've seen others also get
tripped up by this too, as they also were not
aware until afterwards. So, I have tried to
include the common ones into the template.
I have also prepared a layout that would
ensure a more uniform experience when
looking through Pull Requests, with expected
headings and the ability to provide the
instruction of what to put under each heading.
Minor grammar and punctuation edits as well.
If the layout is preferred as a seperate Pull
Request, let me know and I will do so.
Will also update the CONTRIBUTING.md
file to achieve the same goal as well.
Signed-off-by: Joshua Criss <owlsy@outlook.com.au>
Josef Schlehofer
Joshua Criss
Paul Donald