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

"You deploy from master to master" error for organization type repository #363

Closed
padhia opened this issue Jun 22, 2020 · 5 comments
Closed
Assignees
Labels

Comments

@padhia
Copy link

padhia commented Jun 22, 2020

Check list before opening this issue

Describe your question

I have an organizational repo for which I am trying to publish Github pages. I followed this document. The action fails with the error message mentioned in the title. I am not sure what am I doing wrong here.

Link to your contents

Repo: https://github.com/raas-garba/raas-garba.git
Workflow: https://github.com/raas-garba/raas-garba/blob/master/.github/workflows/pages.yml

Screenshots

Additional context

@padhia padhia added the support User support label Jun 22, 2020
@peaceiris
Copy link
Owner

Your operation will break your content. You can use the gh-pages branch to deploy your site instead of the master branch.

@padhia
Copy link
Author

padhia commented Jun 22, 2020

Thanks for the quick response. Of course, I don't want my source code to be overwritten by the generated HTML. Mine is an Organization Type repository. Maybe I am missing something, this example uses master branch in the documentation. Is publishing repository name not automatically derived as <repo>.github.io? Do I need to specify that as an external repo?

@peaceiris
Copy link
Owner

You have two ways:

  1. Deploy your site from raas-garba/raas-garba to raas-garba/raas-garba.github.io using the external_repository option
  2. Move the master branch of raas-garba/raas-garba to another branch of raas-garba/raas-garba.github.io (e.g. source branch)

@padhia
Copy link
Author

padhia commented Jun 22, 2020

That fixed it. Thanks!

@github-actions
Copy link
Contributor

This issue has been LOCKED because of it being resolved!

The issue has been fixed and is therefore considered resolved.
If you still encounter this or it has changed, open a new issue instead of responding to solved ones.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants