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

BF/IMP: Fix the Github Pages deploy #282

Open
thebeline opened this issue Mar 30, 2021 · 0 comments
Open

BF/IMP: Fix the Github Pages deploy #282

thebeline opened this issue Mar 30, 2021 · 0 comments

Comments

@thebeline
Copy link
Contributor

Best I can tell is this is being triggered because we have a /docs/ directory. It would be my opinion that we either fix things so that this actually deploys a working website (currently... it doesn't), or figure out where the settings are to disable this deployment process.

Personally, I would think the project would want a website, but that is just me.

Frankly, if that was the route, the correct order of operations would probably be to create a new Organization of the name OctoScreen, which would afford that organization the TLD octoscreen.github.io, and have the the UI, OctoPrint Plugin, and the forked versions of Go Modules, in that organization.

The project having it's own website would be a HUGE value-add IMHO, and having it under it's own organization would open a few doors as well.

Again, just my opinion. The other option is really to just scrap that deploy process.

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

1 participant