Change default branches to main about blueprint HOT 15 CLOSED

I'd rather just create one issue with a checklist for all repos. Off the top of my head, some of the kfdefs will need to be updated and any links in docs throughout the org. And down stream repos linking via remote references (aicoe-cd comes to mind). Shouldn't be too bad imo.

from blueprint.

@larsks -- yes some of the files here will need to be updated, as they reference the app repo itself for odh manifests. Example.

from blueprint.

Yes, I think we should adapt to the new standard and update our default branches to main.

from blueprint.

What's a good plan of action? Create issues on all repositories and slowly port them over?

from blueprint.

I'm good with that, should I just add a checklist to this issue? or create a new one in the blueprints repo?

from blueprint.

Currently we have a mix of main and master branches in our repos. I think it would be nice to unify it. 👍

I think we can add the checklist to this issue. There's no point to have multiple issues for the same task.

Additional points to @HumairAK's:

• Change Travis build config for the website
• Update srcLink for Gatsby nodes for the website

from blueprint.

I came up with the following checklist -- wdyt?

• apps
  • Update kfdefs to point to correct repositories
• SRE
• operate-first.github.io
• support
• argocd-apps
• workshop-apps
• continuous-deployment
  • Update remote references in downstream aicoe-cd repository
• blueprint
• toolbox
• continuous-delivery
• odh-dashboard
• Change Travis build config for the website
• Update [srcLink](https://github.com/operate-first/operate-first.github.io/blob/a7d9e652a3a5634223892f89b5fa695e9a7710c1/gatsby-node.js#L41-L45) for Gatsby nodes for the website
• Update links in the docs websites to new locations
• continuous-deployment's remote reference for apps of apps

from blueprint.

support, blueprint, workshop-apps, and argocd-apps repos already use main as the default branch, those points are invalid

from blueprint.

nice! 4 items on the checklist can already be checked off :-D

from blueprint.

Is there anything preventing us from just renaming the default branch on the apps repository? It looks as if all the configurations that point there are using HEAD, so they should follow the change without a problem.

from blueprint.

Added continuous-deployment's remote reference for apps of apps to the list

from blueprint.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

from blueprint.

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

from blueprint.

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

from blueprint.

@sesheta: Closing this issue.

from blueprint.