Closed IanButterworth closed 12 months ago
Looking at the only 3 error reports of Resource not accessible by integration since #264 they all were missing the new permissions.
Resource not accessible by integration
So this tries to give more targeted feedback to the user, without erroring.
If 403's turn out to be only tied to bad perms now perhaps this could be changed to a disallowed error and actually throw on the action. But that's premature.
Note that https://github.com/JuliaRegistries/TagBotErrorReports/issues/101#issuecomment-1696706158 was fixed by updating the perms https://github.com/vchuravy/HashArrayMappedTries.jl/commit/39c45bc8293b0e56fc57a01b777595662d85baa6
Bump @christopher-dG
Let me know if I should just proceed with things like this
Looking at the only 3 error reports of
Resource not accessible by integration
since #264 they all were missing the new permissions.So this tries to give more targeted feedback to the user, without erroring.
If 403's turn out to be only tied to bad perms now perhaps this could be changed to a disallowed error and actually throw on the action. But that's premature.