You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a channel where people like to talk about numbered stuff in contexts other than issues, it's pretty easy to trigger errors from sopel-github when a number higher than the maximum issue/PR number in the linked repo is mentioned.
We should suppress "[GitHub] API says this is an invalid issue" errors for inline refs without a (user/)repo attached.
The text was updated successfully, but these errors were encountered:
Errors are blanket-suppressed with #136. For a more nuanced approach, as noted in that PR, it would be better to wait until after some long-overdue code cleanup/refactoring can happen.
In a channel where people like to talk about numbered stuff in contexts other than issues, it's pretty easy to trigger errors from sopel-github when a number higher than the maximum issue/PR number in the linked repo is mentioned.
We should suppress "[GitHub] API says this is an invalid issue" errors for inline refs without a (user/)repo attached.
The text was updated successfully, but these errors were encountered: