Added feature pre-commit

[kush34]

Contributor checklist

• This pull request is on a separate branch and not the main branch

---

Description

Added Pre-commit feature: This feature runs our hooks on every commit to automatically point out issues in code such as missing semicolons, trailing whitespace, and debug statements. Pointing these issues out before code review makes the process easier.

Related issue

• Add pre-commit hooks and checks to the project #137

[github-actions]

Thank you for the pull request!

The Scribe team will do our best to address your contribution as soon as we can. The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and Data rooms once you're in. Also consider joining our bi-weekly Saturday dev syncs. It'd be great to have you!

Maintainer checklist

• The commit messages for the remote branch should be checked to make sure the contributor's email is set up correctly so that they receive credit for their contribution

  • The contributor's name and icon in remote commits should be the same as what appears in the PR
  • If there's a mismatch, the contributor needs to make sure that the email they use for GitHub matches what they have for git config user.email in their local Scribe-Data repo

• The CHANGELOG has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

[andrewtavis]

You can remove this commented out Prettier code here, @kush34 :) We're not using it in Scribe-Data.

[andrewtavis]

No stress on the Mac OS build, btw @kush34 :) We have some problems with those right now.

Generally this all looks good! The JSON files that have all of these changes are going to be moved out of Scribe-Data at some point anyway. Do you want to mark it as ready for review?

[andrewtavis]

Feel free to send along another commit to remove the commented out code that I mentioned here, but aside from that it should be fine :)

[andrewtavis]

I'm going through and trying to close things now, @kush34, so will actually mark as ready and bring it in :) Hope that's ok!

[andrewtavis]

Thanks for setting this up, @kush34! Appreciate the quick work here. Really excited to have this in the project now!