-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update CONTRIBUTING.md #857
Conversation
* fix capitalisation of: ** "Core Contributors" ** "Technical Team"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thank you! Some minor comments included.
capitalize heading Co-authored-by: Stefan Münnich <stefan.muennich@unibas.ch>
fix typo Co-authored-by: Stefan Münnich <stefan.muennich@unibas.ch>
fix typo Co-authored-by: Stefan Münnich <stefan.muennich@unibas.ch>
fix capitalisation of heading
just spotted an outdated section on TravisCI thus converting to draft |
can't find what I was wondering about with that, please proceed with reviewing |
found it rephrased it to match the current GitHub Actions CI. |
Co-authored-by: Stefan Münnich <stefan.muennich@unibas.ch>
add workflow
CONTRIBUTING.md
Outdated
|
||
When a new pull request comes in, the TravisCI service will automatically build the schema using the TEIC Stylesheets, and then validate the test files and the sample encodings against the built schemas. If, for some reason, a change breaks the schema build, or breaks validation, TravisCI will report an error on the pull request. It is then up to the original contributor to fix the issue and submit the fix to the pull request. | ||
When there is a new push to the develop branch, a GitHub Actions workflow will automatically build the MEI schema files and guidelines and publish them at: https://github.com/music-encoding/schema/tree/main/dev |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, missed this before: Is it correct that the guidelines are published at the schema repo? Should we better mention the guidelines repo, too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thx for spotting missed that on :-o
add guidelines repo reference
Sorry, thought that I had pushed the merge button :/ Thanks for the update. |
** "Core Contributors"
** "Technical Team"