docs: add contributing guidelines #95
Merged
+313
−49
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hestro
previously approved these changes
Nov 7, 2026
There was a problem hiding this comment.
This is very professional and thorough! The guidelines make a really nice reference for the team, and I like having it all in one place. I agree with all the points you have covered!
Maybe issues should also have assignees, labels, etc. as a SHOULD, like the PR section has?
|
Good idea. Added this now, along with making milestones optional if there aren't any. However, we have milestones set up all the way until the project deadline, so we will continue using these either way |
|
Looks good, nice to have all of this in one place! |
johahor
approved these changes
Nov 10, 2026
Sign in
to join this conversation on GitHub.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a
CONTRIBUTING.mdfile with guidelines for the following:This PR adds documentation that impacts how we work, therefore we should have everyone read this and be on board before we merge.
Closes #94