Closed duggalsu closed 1 year ago
@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
will do this once the dataset task is written. So ideally next Monday/Tuesday
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.
These are the folders we can move out:
@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.
The following was done to move the folders to another repo.
$ git clone git@github.com:tattle-made/Uli.git
$ cd Uli
$ git config user.name "<user name>"
$ git config user.name
$ git config user.email "
$ git config user.email
- https://github.com/newren/git-filter-repo/blob/main/INSTALL.md
Downloaded python script file in outside folder
$ python3 ../git-filter-repo.txt --path annotators/ --path interrater-scores/ --path ogbv-ml-rest/ --path pooling/ --path scrapers/
- Created new repo here - https://github.com/tattle-made/uli-legacy
$ git remote add origin git@github.com:tattle-made/uli-legacy.git
$ git remote -v
Issues with `git pull origin main` since initial commit with license file exists in newly created repo
* --rebase: gives annotator conflicts
* --ff-only: gives `Diverging branches can't be fast-forwarded`
* --no-rebase: gives `fatal: refusing to merge unrelated histories`
- https://stackoverflow.com/questions/48293820/what-does-no-remote-for-the-current-branch-mean
- https://www.educative.io/answers/the-fatal-refusing-to-merge-unrelated-histories-git-error
$ git pull origin main --no-rebase --allow-unrelated-histories
$ git push -u origin main
Done with PR #488
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