-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate git branch from master
to main
#516
Comments
I was going to open the same issue. I am in favor of main.
…On Sun, Sep 10, 2023 at 5:55 PM Marco Roth ***@***.***> wrote:
Most repositories have migrated to the new main git default. I was
wondering if we should do the same here.
I was reluctant to just to do it because I don't if it would affect
deployments or the like, which is why I open this issue so we can discuss
it.
—
Reply to this email directly, view it on GitHub
<#516>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG7CXL3IBEPEPU5ZR7W3GLXZZOO7ANCNFSM6AAAAAA4SRMECU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Seems like we may not be able to do this as of now, due to GH Pages: |
Oh interesting. I'm actually wondering if this is still the case. Quite some time has passed now 🤔 |
I did very little research. Worth another set of eyes.
…On Tue, Sep 12, 2023 at 2:11 PM Marco Roth ***@***.***> wrote:
Oh interesting. I'm actually wondering if this is still the case. Quite
some time has passed now 🤔
—
Reply to this email directly, view it on GitHub
<#516 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG7CXINH2NE7XXLKXG4Y6LX2DFZXANCNFSM6AAAAAA4SRMECU>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Ok I followed these tips and looks like it seems ok. I have not deleted LMK if it looks ok for others. |
Closing this, as I think everything seems to be working well on |
Most repositories have migrated to the new
main
git default. I was wondering if we should do the same here.I was reluctant to just to do it because I don't know if it would affect deployments or the like, which is why I open this issue so we can discuss it.
The text was updated successfully, but these errors were encountered: