You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 nameOctoScreen
, which would afford that organization the TLDoctoscreen.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.
The text was updated successfully, but these errors were encountered: