Fixing GO entries #1411
Fixing GO entries #1411
Conversation
cmungall
commented
Feb 11, 2025
cmungall
commented
- Fixing URL for GO CAMs (go.model)
- Fixed error in name (Activity not Assembly)
- Fixed URL for GO_REFs
- Fixing URL for GO CAMs (go.model) - Fixed error in name (Activity not Assembly) - Fixed URL for GO_REFs
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1411 +/- ##
==========================================
+ Coverage 42.51% 46.80% +4.28%
==========================================
Files 117 118 +1
Lines 8327 8331 +4
Branches 1963 1354 -609
==========================================
+ Hits 3540 3899 +359
+ Misses 4582 4239 -343
+ Partials 205 193 -12 ☔ View full report in Codecov by Sentry. |
|
thanks @cmungall. I updated your PR to retain the legacy URLs, since they probably appear in sources we want the Bioregistry to support parsing the URLs from. I also added a few more flags for other GO prefixes, perhaps you can do an audit and make a follow-up PR to clarify who's the contact for each GO prefix, what the canonical prefix should be (similar to your request in #1410), and anything else that can improve those records |
|
The json looks good but I'm a bit confused as to why this hasn't propagated to the site yet... |
Sorry about this, it's related to how the bioregistry's CI/CD works. I opened a new issue for fixing this in #1416 |
