luisgulo/focalboard
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
focalboard/docs/contribution-checklist.md
Chen-I Lim ad9e83e8fd
Port contributors guide to GitHub pages (#2296) 
* Port contributor's guide to GitHub

* Fix #2178. Port contributors guide to GitHub pages

* Fix wrong file change

* typo

* Fix link

* Replace PR with pull request

* Remove comment

* Doc at-mention, headings

* Add sudo apt-get install autoconf dh-autoreconf

* database typo

* Update docs/dev-tips.md

Co-authored-by: Doug Lauder <wiggin77@warpmail.net>

* Update docs/index.md

Co-authored-by: Doug Lauder <wiggin77@warpmail.net>

* Update index.md

* Update dev-tips.md

Co-authored-by: Doug Lauder <wiggin77@warpmail.net>
Co-authored-by: Justine Geffen <justinegeffen@users.noreply.github.com>
2022-02-08 13:46:14 -08:00

1.5 KiB
Raw Blame History

Contribution Checklist

Thanks for your interest in contributing code!

Follow this checklist for submitting a pull request (PR):

  1. You've signed the Contributor License Agreement, so you can be added to the Mattermost Approved Contributor List.
  2. Your ticket is a Help Wanted GitHub issue for the project you're contributing to.
    • If not, follow the process here.
  3. Your code is thoroughly tested, including appropriate unit tests, and manual testing.
  4. If applicable, user interface strings are included in the localization file (en.json)
    • In the webapp folder, run npm run i18n-extract to generate the new/updated strings.
  5. The PR is submitted against the main branch from your fork.
  6. The PR title begins with the GitHub Ticket ID (e.g. [GH-394]) and the summary template is filled out.

Once submitted, the automated build process must pass in order for the PR to be accepted. Any errors or failures need to be addressed in order for the PR to be accepted. Next, the PR goes through code review. To learn about the review process for each project, read the CONTRIBUTING.md file of that GitHub repository.