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

Move unmaintained/unused code out of main repo #348

Closed
duggalsu opened this issue Aug 30, 2023 · 8 comments
Closed

Move unmaintained/unused code out of main repo #348

duggalsu opened this issue Aug 30, 2023 · 8 comments
Assignees
Labels
enhancement New feature or request level:ticket An issue that describes a ticket (initiative>feature>ticket) size:2pt

Comments

@duggalsu
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
After setting up dependabot, we are getting a lot of alerts for code we don't use or don't plan to use anymore.

Describe the solution you'd like
Move those projects to a separate repo and archive them if they are not going to be maintained.

Describe alternatives you've considered
None

Additional context
e.g. consider the annotators project for removal

@duggalsu duggalsu added the enhancement New feature or request label Aug 30, 2023
@dennyabrain dennyabrain assigned tarunima and unassigned dennyabrain Oct 25, 2023
@dennyabrain
Copy link
Contributor

@dennyabrain dennyabrain added level:ticket An issue that describes a ticket (initiative>feature>ticket) size:2pt labels Oct 25, 2023
@dennyabrain
Copy link
Contributor

@tarunima you are a blocker on this. If you can take out 30 minutes, we could take it from here. Since its a low priority item, maybe just tell us when you want to work on this. Can set an event invite and work synchronously too. you and @duggalsu need to be on that call. I am optional

@tarunima
Copy link
Collaborator

tarunima commented Nov 1, 2023

will do this once the dataset task is written. So ideally next Monday/Tuesday

@tarunima
Copy link
Collaborator

There are currently four repos relevant to Uli:
Public:

Private:

I expect there will always be a private repo for legacy scripts which we haven't vetted for data risks. But I would like that to be just one and with excellent documentation.

Now for the Uli repo reorganizing, I assume we will have to create more public repos. We want the ML experiments and annotation UI interface to be public. So, we can move these to a separate Uli_legacy repo and put all the unmaintained code there? I don't want to create separate repos for each subfolder.

@dennyabrain
Copy link
Contributor

@tarunima is done with her part. @duggalsu will take over from here.
We'll create a new repository called uli-legacy and move these folders there.

@duggalsu
Copy link
Collaborator Author

The following was done to move the folders to another repo.

$ git clone git@github.com:tattle-made/Uli.git
$ cd Uli
  • git setup
$ git config user.name "<user name>"

# verify
$ git config user.name

$ git config user.email "<email>"

# verify
$ git config user.email
$ python3 ../git-filter-repo.txt --path annotators/ --path interrater-scores/ --path ogbv-ml-rest/ --path pooling/ --path scrapers/
# add remote
$ git remote add origin git@github.com:tattle-made/uli-legacy.git

# verify
$ git remote -v

Issues with git pull origin main since initial commit with license file exists in newly created repo

$ git pull origin main --no-rebase --allow-unrelated-histories

# did a git commit via gui with auto-added commit message

$ git push -u origin main

@duggalsu
Copy link
Collaborator Author

Done with PR #488

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request level:ticket An issue that describes a ticket (initiative>feature>ticket) size:2pt
Projects
No open projects
Status: Done
Development

No branches or pull requests

3 participants