-
Notifications
You must be signed in to change notification settings - Fork 397
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
chore(docs): add troubleshooting for server errors #344
base: main
Are you sure you want to change the base?
chore(docs): add troubleshooting for server errors #344
Conversation
left a few comments regarding tailing, by the way thanks a bunch @sterlingwes 😃 |
Updated! hope that works. thanks for the weekend review 🙏🏻 |
No problem, thank you very much for contributing! 😃 Ready to merge, just one small last thing, could you squash the commits into one? 🙏 |
Can you use capital letters and punctionation in the bullets for consistency with the rest of the documentation? |
address feedback try to undo whitespace chg address punctuation feedback
dca8bf1
to
07bda5f
Compare
You should really consider changing the default to squash on merge so that force pushing on branches during a review isn't necessary from my other PR:
|
Found it really hard to get basic info on why I was seeing an error page when I loaded the app. Figure these steps might be useful. Would love any tips on how to get the deployment ID in a nicer way than directing them to guess at UDIDs in the URL bar!
These steps helped me get at the problem caused by #343