Skip to content
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

deploydocs default to devbranch="master", although github default branch is main now. #1485

Closed
lrnv opened this issue Nov 23, 2020 · 2 comments

Comments

@lrnv
Copy link

lrnv commented Nov 23, 2020

Everything is in the title. I dont know if you want to fix this, as the switch to main instead of master is quite recent.

Just to give you a heads'up :)

@KristofferC
Copy link
Member

Dup of #1443 :)

@andreasvarga
Copy link

Sorry for interfering in this discusion, but recently I faced this problem with a new repository. While the deploydocs failed, other issues have been correctly handled by github, by using for master, if not existing, automatically main.
I wonder if this strategy could also be adopted for deploydocs, for which main is now the natural candidate as default. So, master can be automatically used in the case main is not present.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants