-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Lando init Pantheon recipe default to "main" branch but Pantheon build pipeline only works on "master" #134
Comments
Assuming you've resolved this issue by now. If the issue persists, and updating Lando does not resolve it, please re-open this issue and provide more details. |
I just initiated a new D10 project and the same problem is still there. Steps to reproduce
Current workaround - switch to master branch immediately after the lando init. |
@ethangeorgi it doesn't look like I have permission to reopen this issue. |
I did replicate this and took a look into the code. AFAIK, Lando doesn't do anything "extra" to set the default remote branch when initializing a project. Instead, the problem seems to be that Pantheon has chosen Lando's |
@reynoldsalec I agree that Pantheon should fix this given your analysis. I'll open a pantheon support ticket and point to this ticket for reference so they get the chance to fix it their end. |
I've made a customer support ticket, not public but the ID is 925842 for general reference. It would be good if we could leave this ticket open until we get some info from Pantheon on what they intend to do. |
Sounds good, thanks for following up on it @mrspiderbrain! |
Currently lando init pantheon recipe fails. Default to main branch which does not connect to the cloud build process. Pantheon are planning to move to "main" but not yet.
The text was updated successfully, but these errors were encountered: