Skip to content
This repository has been archived by the owner on Jul 11, 2023. It is now read-only.

Migrate to gitlab #997

Open
6 of 10 tasks
emthompson-usgs opened this issue Sep 26, 2022 · 3 comments
Open
6 of 10 tasks

Migrate to gitlab #997

emthompson-usgs opened this issue Sep 26, 2022 · 3 comments
Assignees
Labels
feature Major new feature

Comments

@emthompson-usgs
Copy link
Member

emthompson-usgs commented Sep 26, 2022

Need to:

  • Clone repo to gitlab
  • Remove all c/cython
  • Remove usernames from documentation
  • Remove links to azure in readme
  • Gitlab repo needs to be released
  • Add link to gitlab url in readme
  • Indicate new repo urls in documentation.
  • Update the doi link to point to gitlab
  • Migrate issues to gitlab
  • Archive github repo
@emthompson-usgs emthompson-usgs added the feature Major new feature label Sep 26, 2022
@emthompson-usgs emthompson-usgs self-assigned this Sep 26, 2022
@emthompson-usgs
Copy link
Member Author

I think we are getting pretty close to moving to gitlab. Also, I'm thinking some of these steps are overkill. For groundfailure, we just sent in a merge that deletes everything except the readme (and some of the admin files) and modified the readme to point to the new repo in gitlab. This seems like a reasonable and easier approach.

@gferragu
Copy link
Collaborator

gferragu commented Nov 1, 2022

@emthompson-usgs the re-designation as a read-only public archive is a nice Github feature, does a warning get printed if you try interacting with the archived remote from the CLI?

@emthompson-usgs
Copy link
Member Author

It does not appear that there is a warning. However, I think that the fact that all functional code has been removed from the repo would prevent anyone from accidentally continuing to use it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature Major new feature
Projects
None yet
Development

No branches or pull requests

2 participants