You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the contributing doc doesn’t fully align with our current practices. I think it would be helpful to have a discussion about which practices we want to enforce and whether there’s anything new we should add, such as using conventional commit prefixes for PR titles. I haven’t always followed what’s in the specified in the docs, so it would be great to align on expectations and make it easier for everyone to follow.
I think it would be really great to have a discussion about GKS contributing guidelines and what they should include.
Proposed Action Items:
Review examples of effective contributing guidelines from open-source projects
Draft a new CONTRIBUTING.md file with proposed guidelines
Create PR
Required Skills
Experience with Markdown + experience contributing to open-source projects
The text was updated successfully, but these errors were encountered:
Submitter Name
Kori Kuzma
Submitter Affiliation
No response
Project Details
I created this issue in the VRS repo:
I think it would be really great to have a discussion about GKS contributing guidelines and what they should include.
Proposed Action Items:
Required Skills
Experience with Markdown + experience contributing to open-source projects
The text was updated successfully, but these errors were encountered: