[MAINT] enable nilnesserr linter

[deiga]

---

Before the change?

• Code could be checking for if err != nil but return a different error

After the change?

• Linter will mark that every checked error is being returned correctly

Pull request checklist

• Schema migrations have been created if needed (example)
• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

• Yes
• No

---

[github-actions]

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

[stevehipwell]

I like this idea, minor nits to fix.

FYI we still have a core linter disabled which need the code updating to re-enable it.

[deiga]

I like this idea, minor nits to fix.

FYI we still have a core linter disabled which need the code updating to re-enable it.

Yeah, I tried enabling it and was overwhelmed 😂

[stevehipwell]

LGTM

[stevehipwell]

LGTM