GenomicsStandardsConsortium
Update CONTRIBUTING.md
Started the extension of the CONTRIBUTING.Md doc - more content should be added so devs know what and how to edit to maintain and extend MIxS.
Closes #615
@turbomam @sujaypatil96 - this PR targets main.
Is that right or is there a branch to stage the release?
@pbuttigieg: there's a merge conflict. Do you prefer for the issues and pulls links to appear before or after your new text about modifying mixs.yaml?
Before - that information is more general than my additions, so should appear first
I resolved the merge conflict by placing @pbuttigieg's new content after the links about issues and pull requests
@pbuttigieg I think I havw covered or will cover this content in https://github.com/GenomicsStandardsConsortium/mixs/tree/606-mixs-editing-workflow-and-policy. May I close this PR without merging?
@ramonawalls
I think I havw covered or will cover this content in https://github.com/GenomicsStandardsConsortium/mixs/tree/606-mixs-editing-workflow-and-policy. May I close this PR without merging?
This linked to a long-running branch with many changes from multiple people. I made a PR for this to make it easier to see the changes:
https://github.com/GenomicsStandardsConsortium/mixs/pull/617/files
However, it looks like @pbuttigieg's PR has independent and useful contributions on how to find the yaml file to edit, etc, so I would like to merge this.
Also, can I make a plea for
- smaller, incremental PRs
- breaking larger pieces of work into smaller
- no long running branches
- always having a PR for each branch to make it more visible
- faster decisions and merges on smaller PRs
Otherwise things get out of sync. This PR is from October. The linked PR is from 5 months ago. All of the good work in these PRs is not yet visible on the site. I know it's hard as we are volunteering time but some simple changes in practice can help us make use of our time more effectively
