docs(README): add example for error handling

[till]

As discussed: octokit/octokit.js#2039

[nickfloyd]

Hey @till, Thanks for this change! ❤️ . The doc looks good content-wise but has some linting issues. Could you either:

1. Update this to reflect what I mentioned above and push the update to this PR or...
2. Set the fork to give maintainers write access and I'd be glad to make the change for you!

[till]

Hey @till, Thanks for this change! ❤️ . The doc looks good content-wise but has some linting issues. Could you either:

1. Update this to reflect what I mentioned above and push the update to this PR or...
2. Set the fork to give maintainers write access and I'd be glad to make the change for you!

Hey @nickfloyd — allow edits from maintainers is already checked (I see it right next to this field). So feel free to change as needed. I don't see the exact issues as prettier doesn't say in the log and because I don't have a local clone. But your help is appreciated. :)

[nickfloyd]

Hey @till, unfortunately, I don't have write access to your fork.

You don't have write access to the till/request-error.js repository, so you cannot push changes to it.
To obtain write access we will point this codespace at your fork of till/request-error.js, creating that fork if it doesn't exist.

Can you run npm run lint:fix from your fork and commit the changes?

[till]

I did, committed and squashed. LMK

[till]

Btw, any idea what this means?

[nickfloyd]

Btw, any idea what this means?

That is the console message that you'll get when maintainer access is not enabled on a fork.

[till]

@nickfloyd no, no, at the right [x] Allow edits by maintainers — it was checked all along. Was just curious. Anyway, thanks for merging.

[github-actions]

🎉 This PR is included in version 4.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀