Change the name of the branch in all notify repos to 'main' about notification-api

[AntoineAugusti]

The main problem is with our deploy pipeline https://github.com/cds-snc/notification-pr-bot/blob/aa7a3a15129dd3dd48111c4f82ab7b50f643d9de/index.js#L17-L43 and Kubernetes https://github.com/cds-snc/notification-manifests

[AntoineAugusti]

Related to cds-snc/notification-admin#1020 cds-snc/notification-pr-bot#16 cds-snc/notification-document-download-frontend#55 cds-snc/notification-document-download-api#38

[dj2]

For the PR bot, what happens if there is an entry in there for a branch that doesn't exist? Do we know if the bot will just ignore it? If it does, we could add 'main' alongside 'master' in the list and then remove 'master' post deploy.

If it doesn't support it .... do we control the code, could I make it supported?

For Kubernetes, I don't have knowledge of kubernetes so I don't know how hard it would be to migrate. Do you deploy on every push? Could we prepare the kubernetes change in a branch that gets committed soon after the changes to other repos?

[yaelberger-commits]

@jzbahrai can you please have a look at this one? Thanks

[HEYGUL]

I have the feeling this issue could be closed (main branch seems now alive instead of master).

[jimleroyer]

Yes, the mainline branch for all our active projects are now in main for quite some time.