606 mixs editing workflow and policy #789
Open
Conversation
This file contains 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
This file has been replaced by CONTRIBUTING.md in the root directory and the readme file in this directory.
only1chunts
reviewed
Nov 14, 2024
| Please review GitHub's overview article, | ||
| ["Tracking Your Work with Issues"][about-issues]. | ||
|
|
||
| **Labeling issues:** Issue labeld were updated 2023/12. Please do not create new labels on your own. Instead, create an issue to request a new label, which will be reviewed by the TWG or CIG. See the [labels page](https://github.com/GenomicsStandardsConsortium/mixs/labels) for descriptions of existing issues. |
There was a problem hiding this comment.
typo: "labeld" should be "labels"
typo: "for descriptions of existing issues " should read "for descriptions of existing labels"
only1chunts
approved these changes
Nov 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I am creating this PR because there was a long running branch that is referenced from elsewhere and it needs to be made more visible. However I would strongly recommend avoiding long running branches and PRs and instead break things into smaller chunks