How to deploy your github organisation Github Pages while your main account is marked as spam

Sh Raj - Feb 27 - - Dev Community

If you are marked as spam your account losses access to deploy GitHub pages and many more things happen one of the popular error is your previously deployed Pages will remain but no new build process will run.

Disclaimer :- This process is only for if your GitHub account is suspended without mean and you have to perform GitHub Actions untill GitHub Support Fixes the error.

Fix this by :-

  • Go to organisation invite section.
  • And invite your new account(you have to create one)
  • if Github is blocking you to invite go to teams tab and create a team.
  • Invite new user in the team.
  • Give owner access.
  • Now redeploy the GitHub pages of the repo. 404 error will be removed.
  • or create new repos and deploy it to GitHub pages.

Still you can't fix your main account, for that you have to create GitHub Ticket and contact GitHub Support.


Here's a revised version of the article:

If your account is marked as spam, you'll lose access to deploying GitHub pages, among other restrictions. One common issue is that while your previously deployed Pages will remain accessible, any new build processes will not run.

Disclaimer: This process is intended for cases where your GitHub account is suspended in error, and you need to continue using GitHub Actions until the issue is resolved by GitHub Support.

Here's how to resolve it:

  • Navigate to the organization's invite section.
  • Invite your new account (you'll need to create one).
  • If GitHub prevents you from sending invites, visit the "teams" tab and create a new team.
  • Invite the new user to this team.
  • Assign owner access to the new account.
  • Now, redeploy the GitHub pages for your repository. This should remove the 404 error.
  • Alternatively, create new repositories and deploy them to GitHub Pages.

If you are still unable to resolve the issue with your main account, you'll need to create a GitHub Ticket and reach out to GitHub Support for further assistance.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .