Migrate https://github.com/nexB/matchcode-toolkit to https://github.com/aboutcode-org/

aboutcode-org / matchcode-toolkit

A collection of plugins that makes matchcode-related functions available for scancode-toolkit and scancode.io.

1 stars 1 forks source link

Migrate https://github.com/nexB/matchcode-toolkit to https://github.com/aboutcode-org/ #10

Open pombredanne opened 4 months ago

pombredanne commented 4 months ago

@JonoYang this will be the first candidate to move to AboutCode-org on GitHub ... See https://github.com/nexB/aboutcode/issues/136 for full details Can you be the first one to deal with it? Please keep a log of all the details ... I am curious to see if Azure devops still works.

JonoYang commented 4 months ago

@pombredanne

I've moved https://github.com/nexB/matchcode-toolkit to https://github.com/aboutcode-org/matchcode-toolkit using the following steps:

Create empty repo on aboutcode-org
Clone empty repo to system
Add previous repo as remote:
- git remote add old-repo git@github.com:nexB/matchcode-toolkit.git
Merge old repo with new empty repo
- git merge old-repo/main --allow-unrelated-histories
Push to github
Push tags to github
- git push --tags
Recreate releases on new repo

Azure DevOps needs access to the aboutcode-org repos for CI to work.

JonoYang commented 4 months ago

A simpler way to achieve what I did above:

Transfer the nexB repo to the aboutcode-org organization from Settings -> Danger Zone -> Transfer ownership
Set up CI for that repo on Azure Devops
- Log into the nexB organization on Azure Devops
- Go to the project that was moved
- On the left hand menu, click on Pipelines, and then delete the existing pipeline
- On the same page, click New pipeline, and then click Github, then select the repo that was transferred to aboutcode-org
- Complete adding the pipeline

mjherzog commented 3 months ago

Guessing that we should just ignore that most repos are based on the nexB skeleton.

mjherzog commented 3 months ago

More steps:

Update org-level permissions
Check org-level permissions for each repo and update repo-level permissions.
Update URLs over time.
Create new PyPI release with updated URLs. So we should create an Issue template / checklist for this and create a nexB org-level project.

pombredanne commented 3 months ago

Guessing that we should just ignore that most repos are based on the nexB skeleton.

Good point... we need to make a test migration with a repo template too.