Skip to content

Latest commit

 

History

History
48 lines (32 loc) · 2.27 KB

CONTRIBUTING.md

File metadata and controls

48 lines (32 loc) · 2.27 KB

Contributing

🥳🤠🎉👍 Welcome to MeetingMinder 👍🎉🤠🥳

Resources

Summary

When contributing to MeetingMinder, if there is not already an issue open, please first discuss the change you wish to make via an issue before making a change.

Please note we have a code of conduct, please follow it in all your interactions with the project.

Testing

Frontend:

  • Spend some time testing what your changes affected.
  • Try to break your own feature.
  • Think about edge cases.

Backend:

  • Make sure any additional features or changes to existing features are covered under the tests in api/test/tests
  • Run npm run test in console and confirm all tests are passing
  • Ensure changes function as expected on the front end

Pull Request Process

  1. Write your pull request description according to the pull request template
  2. Assign your pull request to a SocexSolutions developer under the github assign tab. This developer will handle assigning reviewers
  3. Reply to discussions. There may be cases where a developer requests a change before the Pull Request can be merged.
  4. You may merge the Pull Request in once you have the sign-off of one other SocexSolutions developer, or if you do not have permission to do that, you may request the reviewer to merge it for you.

Bug Reports

Before Reporting

  • See if you can find the cause of the problem. You might be able to fix the problem and score an easy contribution
  • Check the issues page for similar existing bug reports

Submitting a Report:

  • Navigate to issues and click New issue
  • Use a clear and descriptive title describing the bug you are seeing
  • Select the bug issue template and fill out the form

Thanks for being a part of MeetingMinder!