wildebeest icon indicating copy to clipboard operation
wildebeest copied to clipboard

chore(docs): add missing troubleshooting step

Open sterlingwes opened this issue 2 years ago • 7 comments

Fixes https://github.com/cloudflare/wildebeest/issues/341 when trying to follow the reset troubleshooting steps and the deploy UI doesn't prompt for all of the GH Action inputs

sterlingwes avatar Feb 25 '23 22:02 sterlingwes

It didn't, that's the reason I opened this

sterlingwes avatar Feb 27 '23 13:02 sterlingwes

@sterlingwes could you please go on https://deploy.workers.cloudflare.com, clear your browser's cache / cookies and try the deploy button again? the fields should show up.

xtuc avatar Feb 27 '23 13:02 xtuc

I did that as per the linked issue, multiple times. Have you tried yourself?

Used chrome and tried incognito and cache clearing

sterlingwes avatar Feb 27 '23 14:02 sterlingwes

Using chrome: image

Do you see any errors in the console?

xtuc avatar Feb 27 '23 14:02 xtuc

Thanks for checking

New day, new brain.. and looks like I missed that the deploy button tags on a bunch of query params which are necessary for those fields to show. Those params are stripped from the "done" page URL and they're also not present in the link in the troubleshooting doc, which is I think why I ended up retrying incognito on that link (https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/wildebeest)

I'll update this PR to suggest users go back to the deploy button on the Getting Started doc if you think that would be useful?

sterlingwes avatar Feb 27 '23 18:02 sterlingwes

Could you remove the link from the troubleshooting doc and redirect users to the get started guide? So we only have one link and it's the correct one. cc @celso

xtuc avatar Feb 28 '23 09:02 xtuc

In another PR I was asked to squash my commits - have you considered changing the default for the repo to squash on merge? That seems to be the standard nowadays since it encourages PRs to be about one thing (leading to one commit on main, but still allowing for granular commits on the branch and not interrupting the review with force pushes) which is a good practice

Also lowers the contribution barrier to entry.. i find myself less enthused about contributing anything substantial to this repo when it's so much back and forth over smol readme changes

sterlingwes avatar Feb 28 '23 14:02 sterlingwes