Add more informative error message when wiki doesn't exist about actions-wiki HOT 6 CLOSED

I was thinking about granularly saying what was the issue, but, yeah, one single catchall error message like "please enable the repo and make an initial page" would probably be good enough.

Nitpick: we might try checking if the repo exists in a separate step.

This is because I just generally prefer a doThing if valid else fail pattern to try doThing catch fail. Though I'll admit this is more nitpicky, and not that related to performance, when bash scripting.

from actions-wiki.

Doesn't really matter 🤷‍♂️

I notice a lot of code issue things are piling up, so I guess it's time to actually do #23 and get on it 👨‍💻👨‍💻

from actions-wiki.

I think this is overdue:

@all-contributors add @jcbhmr for ideas

from actions-wiki.

Just double-checked since I thought it was pretty weird that the repository doesn't even exist until the initial page is created.

https://docs.github.com/en/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages#cloning-wikis-to-your-computer

Once you've created an initial page on GitHub, you can clone the repository

We can at least use a GraphQL query to detect if the wiki is enabled (it can probably be gotten from the REST API, too).

I was hoping to be able to automatically create the initial page 😞
Apparently there aren't any API endpoints, either, from my quick search, to create an initial page.

from actions-wiki.

I don't even think you need to do that! You can just git <whatever> | grep -i 'remote: repository not found' and if it matches, you know that the repo wasn't found, therefore, show a more informative error message.

from actions-wiki.

@spenserblack

I've put up a pull request to add @jcbhmr! 🎉

from actions-wiki.