For me it was the only way. I get an error when I try to push to master in this way
Il lun 26 apr 2021, 19:32 Andrea Cosentino <anco...@gmail.com> ha scritto: > The only way I see is dropping the master branch from your local > repository > > Il lun 26 apr 2021, 19:30 Claus Ibsen <claus.ib...@gmail.com> ha scritto: > >> Hi >> >> Old habits die hard, I just pushed a commit to master. >> >> I wonder if there is maybe a way to make that invalid or that "master" >> branch is locked or something, so you get an error, and then remember >> its main instead. >> Anyone know of what others may have done with this problem. >> >> On Thu, Apr 8, 2021 at 2:20 PM Andrea Cosentino <anco...@gmail.com> >> wrote: >> > >> > Hello, >> > >> > I think we need some coordination in the renaming of master branches to >> > main in all of our repositories. >> > >> > I think we need to come up to INFRA with a list of repos we want to >> move to >> > main. >> > >> > Then we need to check every reference in Jenkins or gh actions and >> align. >> > >> > It doesn't really make sense to rename just a couple of repositories in >> > subprojects of the ecosystem. >> > >> > So I think we need to list what repositories are now missing. >> > >> > We have: >> > camel-quarkus done >> > camel-website done >> > >> > We are missing: >> > camel >> > camel-example (x 3) >> > camel-k >> > camel-k-examples >> > camel-k-runtime >> > camel-kafka-connector >> > camel-kafka-connector-examples >> > camel-performance-tests >> > >> > probably more. I need to complete the list. >> > >> > Thoughts? >> >> >> >> -- >> Claus Ibsen >> ----------------- >> http://davsclaus.com @davsclaus >> Camel in Action 2: https://www.manning.com/ibsen2 >> >
