Switch from `master` to `main` branch in all AsyncAPI repos

[derberg]

Related to https://github.com/asyncapi/community/discussions/140 We first identify what is needed to do. Then we will ask TSC if we should proceed

Things to do:

• [ ] Organization settings for Repository defaults change to main
• [ ] First we need to adapt .github repo:
  • [ ] change master to main
  • [ ] update this workflow.
  • [ ] we need the following workflows to update to support both, master and main: 1, 2, 3, 4. We cannot just switch to main as these workflows will be automatically updated in all the repositories, where we later need to make changes to default branches.
  • [ ] update some markdown files listed here

🆘 Things that I have no idea about are like: is https://github.com/asyncapi/.github/blob/master/git-workflow.md going to work once we change the branch name? some redirect will be created by GitHub?

Please provide more points in the comments and I will update the checklist above. Make it as easy for me as possible in a checklist form, so I just copy/paste 🙏🏼

[jonaslagoni]

Some repositories will have their own set of workflows as well, so we need to make sure that custom workflows are checked. At least I know Modelina have, not sure about others 🙂

[jonaslagoni]

Those are all repositoes that have custom workflows:

@smoya not sure how you generated it, but I cannot find automerge-release-pr-bump anywhere 🤔 i.e. https://github.com/asyncapi/html-template/tree/master/.github/workflows/automerge-release-pr-bump.yml is not a thing and nowhere to be found https://github.com/asyncapi/html-template/tree/master/.github/workflows. I assume the same for any of the repositories.

Also, it is missing Modelina, so not sure if others are missing as well 😄

[smoya]

Here is the list of repositories that contain workflow files not included in .github org repository: https://gist.github.com/smoya/4617304ec510c6f13e2bb9978b0ec824#file-result-md

[jonaslagoni]

Here is the list of repositories that contain workflow files not included in .github org repository: https://gist.github.com/smoya/4617304ec510c6f13e2bb9978b0ec824#file-result-md

That's more accurate 😄 I guess you can add that to the list of things todo @derberg

[derberg]

it is not much accurate, it is actually scary only 😛

there are all workflows, even those that do not react on event-related to commit to master - example https://github.com/asyncapi/temp-repo-test-for-website/blob/master/.github/workflows/issue-pull-request-upvote.yaml

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart:

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart:

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart:

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart:

[AnimeshKumar923]

@derberg hey, I'm ready to work on this. Or is this only possible for CODEOWNERS/maintainers?

[derberg]

that is a gigantic task that you can work on but must be coordinated and done in short time frame