Repository navigation
BundleMon v2 project migration #125
Description
Activity
- pinned this issue
on Aug 20, 2022 Owner: Leaflet
Repo: Leaflet
Project ID: 61e0545915f6c3000980d0edOwner: Creditas
Repo: creditas-site
Project ID: 6166d779ea62d600083a9223Hello, we have 2 projects using bundlemon that need migration:
Owner:
tem-energy
Repo:control-room
Project ID:62dea945130f8841fa8727b9Owner:
tem-energy
Repo:portal-spa
Project ID:62d1385f6a9efbea2f808caaThanks in advance 👍🏻
@bartelemi done
Reacted by Bartłomiej SzostekHi we have 2 projects, it would be great if you could port them
Owner: gemini-hlsw
repo: explore
project ID: 61a698e5de59ab000954f941Owner: gemini-hlsw
repo: lucuma-core
project ID: 62d5c1243fb16506944581f2Thanks a lot
Hi thanks, sorry my bad the project was lucuma-catalog
Reacted by LironErOwner: dpietrzyk
Repo: chef
Project ID: 6238dd074aa889d079ea47ca@dpietrzyk done
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