Replies: 3 comments
-
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Here's the concise text solution for the GitHub Pages REST API issue: First, make a POST request with build_type=workflow This two-step process will successfully create and deploy your GitHub Page without needing to manually create the gh-pages branch. |
Beta Was this translation helpful? Give feedback.
-
Problema atual: Ao tentar criar uma página do GitHub usando a API REST com o caminho de origem configurado como '/', a solicitação POST falha com um erro indicando que a ramificação 'gh-pages' precisa ser criada primeiro. Isso ocorre apesar da documentação sugerir que a criação da ramificação não é necessária. Solução/alternativa: Primeiramente, envie uma solicitação POST com o parâmetro build_type=workflow. Observação: Parece haver uma discrepância entre a documentação da API e o comportamento atual da implementação. Seria interessante considerar a abertura de um relato de problema sobre isso na documentação do GitHub. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Bug
Body
Trying to create a new GitHub Page from the REST API with the source path set to
/
should work according to the documentation. In actuality, it returns an error that you have to create agh-pages
branch first.The workaround for this is that you have to first
POST
withbuild_type=workflow
and then switch over tobuild_type=legacy
deploy via aPUT
request.Beta Was this translation helpful? Give feedback.
All reactions