chore: add contribution guidelines to readme

Author: samuelOsborne

.github/workflows/release.yml

@@ -2,7 +2,7 @@ name: Release
 
 on:
   push:
-    branches: [develop]
+    branches: [master]
 
 jobs:
   build:

README.md

@@ -255,6 +255,37 @@ Seek to a given frame. Frame value can be a number or a percent string (e.g. 50%
 
 Type: `void`
 
+## Contributing
+
+We use changesets to maintain a changelog for this repository. When making any change to the codebase that impacts functionality or performance we require a changeset to be present.
+
+To add a changeset run:
+
+```
+yarn run changeset
+```
+
+And select the type of version bump you'd like (major, minor, path).
+
+You can document the change in detail and format it properly using Markdown by opening the ".md" file that the "yarn changeset" command created in the ".changeset" folder. Open the file, it should look something like this:
+
+```
+---
+"@lottiefiles/pkg1": minor
+"@lottiefiles/pkg2": major
+---
+
+This is where you document your **changes** using Markdown.
+
+- You can write
+- However you'd like
+- In as much detail as you'd like
+
+Aim to provide enough details so that team mates and future you can understand the changes and the context of the change.
+```
+
+You can commit your changes and the changeset to your branch and then create a pull request on the develop branch.
+
 ## License
 
 MIT License © LottieFiles.com