Skip to content
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

Movement of refget from hts-specs to GA4GH refget #816

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

andrewyatz
Copy link
Contributor

As part of approval for refget sequence collections, we have created a new repository for refget under the GA4GH GitHub space. This PR denotes the current supported location is in the new location but retains the v2.0.0 spec here for reference.

Moving to the new GA4GH GitHub Repository https://github.com/ga4gh/refget
@jkbonfield
Copy link
Contributor

We should probably remove it from the README file (or point it elsewhere) and similarly the http://samtools.github.io/hts-specs/ site too.

@jmarshall
Copy link
Member

jmarshall commented Feb 19, 2025

If refget wishes to move, then it should do so properly IMHO and remove the soon-to-be-outdated text. I have activated jekyll-redirect-from in this repository, so (after rebasing on current master) you can replace all of refget.md with simply

---
redirect_to: https://ga4gh.github.io/refget/sequences/
---

You should also either remove the refget paragraph in README.md or (better) change the link and add text saying that it is now maintained elsewhere; remove the refget line in index.md; delete pub/refget-openapi.yaml and pub/ga4gh_and_TRUNC512_identifiers.*. You may also wish to remove the refget entry from MAINTAINERS.md.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants