json-schema-validator icon indicating copy to clipboard operation
json-schema-validator copied to clipboard

Published 20 hours ago • verified publisher icon pboettch

Question: was the default branch recently renamed to "main"?

Open greenfoo opened this issue 2 years ago • 6 comments

Hi, sorry for opening a ticket for a question but I'm trying to figure out why Yocto's build system broke on this repo and it might be related to the default branch name.

Was the default branch name changed from "master" to "main" recently (~in the last 24 hours)? (that would explain what I'm seeing).

Thanks!

greenfoo avatar Jun 06 '22 15:06 greenfoo

Yes. Sorry. I had no mean to inform users or at least I'm not aware of any good way to do so on GitHub.

On June 6, 2022 5:55:46 PM GMT+02:00, greenfoo @.***> wrote:

Hi, sorry for opening a ticket for a question but I'm trying to figure out why Yocto's build system broke on this repo and it might be related to the default branch name.

Was the default branch name changed from "master" to "main" recently (~in the last 24 hours)? (that would explain what I'm seeing).

Thanks!

-- Reply to this email directly or view it on GitHub: https://github.com/pboettch/json-schema-validator/issues/204 You are receiving this because you are subscribed to this thread.

Message ID: @.***> -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

pboettch avatar Jun 06 '22 16:06 pboettch

Thanks for the confirmation! (I need to notify rdkbcentral now so that they can update the reference)

greenfoo avatar Jun 06 '22 16:06 greenfoo

Sorry for the trouble. I really wasn't aware (and still not) how to do this smoothly.

pboettch avatar Jun 06 '22 20:06 pboettch

~~Hi @pboettch , I know this might be too much to ask (so feel free to ignore my request), but ... would it be possible to revert back to "master" for a few weeks until I figure out how to fix our internal build system?~~

~~It's not trivial to change the reference due to the way the build system works and it's causing a lot of headaches and emails :)~~

~~Thanks.~~

Forget about this, we finally found a workaround. Thanks!

greenfoo avatar Jun 07 '22 08:06 greenfoo

Didn't saw your edit, I just recreated a master-branch.

pboettch avatar Jun 07 '22 09:06 pboettch

Ok, it will work with both in our work around :)

Are you planning on leaving "master" for others? For example:

  • The main development can go to "main" from now on.
  • The "master" branch exists but remains "stalled"

This way, if someone is interested in new developments he will need to start using "main", but those using commits from older references can keep using "master" and their build systems won't break.

I don't think this is ideal, but at least seems to work :)

Thanks again.

greenfoo avatar Jun 07 '22 09:06 greenfoo

I'm going to drop the master-branch once the release is done (about to happen)

pboettch avatar Nov 26 '22 17:11 pboettch