BundleMon v2 project migration

[LironEr]

BundleMon CLI v2 introduced some breaking changes.

If you are using BundleMon in GitHub actions you don't need to set project ID anymore, BundleMon will automatically create a new project linked to your repo on GitHub.

The old way of using project ID without an API key will stop working in a few months so it's important to upgrade.

If you want to keep your current project history you can reply with your details to this issue or send me an email (lironerm@gmail.com) with the owner, repo name, and your current project id.

Example:
Owner: lironer
Repo: bundlemon
Project ID: aaaaaaaaaaaa

[jonkoops]

Owner: Leaflet
Repo: Leaflet
Project ID: 61e0545915f6c3000980d0ed

[LironEr]

@jonkoops done

[eroSilva]

Owner: Creditas
Repo: creditas-site
Project ID: 6166d779ea62d600083a9223

[LironEr]

@eroSilva done

[bartelemi]

Hello, we have 2 projects using bundlemon that need migration:

Owner: tem-energy
Repo: control-room
Project ID: 62dea945130f8841fa8727b9

Owner: tem-energy
Repo: portal-spa
Project ID: 62d1385f6a9efbea2f808caa

Thanks in advance 👍🏻

[LironEr]

@bartelemi done

[cquiroz]

Hi we have 2 projects, it would be great if you could port them

Owner: gemini-hlsw
repo: explore
project ID: 61a698e5de59ab000954f941

Owner: gemini-hlsw
repo: lucuma-core
project ID: 62d5c1243fb16506944581f2

Thanks a lot

[LironEr]

@cquiroz I migrated the first project (61a698e5de59ab000954f941), but the second is already linked to lucuma-catalog repo

[cquiroz]

Hi thanks, sorry my bad the project was lucuma-catalog

[dpietrzyk]

Owner: dpietrzyk
Repo: chef
Project ID: 6238dd074aa889d079ea47ca

[LironEr]

@dpietrzyk done