-
Notifications
You must be signed in to change notification settings - Fork 3
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
content update | fix typo #16
Comments
If you notice a typo in the register, for example, you notice ‘velocity’ is spelled ‘vecolity’, this is how you can get it changed:
|
During IPET-MDRD-4 meeting, folks spotted a typo ... so I thought I'd try out your process to fix. At step (8) I had the option to 'commit direct to master' ... I guess that's because I've got commit privilege? Other than that, it was quite simple. I'll share this processing with folks tomorrow, time permitting. For reference, see wmo-registers/code-manuals#42 |
Jeremy just demonstrated this - good work! I questioned whether instead of requiring download from the registry and upload of a new file whether it would be better to use the 'normal' github workflow directly on the .ttl files in github. i..e find ttl file that is broken, (if you try to edit a file you don't have access to github automatically offers to create a fork) |
In the
< Contributing to codes.wmo >
section
provide information on how to propose an update fixing a typographical change
The text was updated successfully, but these errors were encountered: