-
Notifications
You must be signed in to change notification settings - Fork 12
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
bug: Resource not accessible by integration #28
Comments
+1 - Your action is awesome, and has worked perfectly for me up until Wednesday.
For reference, here are the complete logs. And this is my workflow file. I guess it's an external change in an API, and not directly related to this action. But it would be great to have an update sometime, so that it can work again. Thank you @JasonEtco for all your work in developing and maintaining is-sponsor-label-action, it's been really useful :) |
I have the same issue indeed |
@JasonEtco - Any update on this? |
this isn't a bug for @JasonEtco to fix. It is being caused by a bug that the GitHub team accidently introduced. The team knows about the issue and has prioritized it for fix. I have no clue what that means in terms of when we can expect it to be resolved, but I would assume once they've fixed it we'll start seeing all new PRs and Issues getting the label properly again. |
I guess this was fixed in #30 by @cheshire137. I tried to reused this PR in kdeldycke/workflows@dfa9ffb but it failed:
I guess this action need special care to be distributed and can't be reused as-is. |
Uh-oh, did I commit some hardcoded |
Oh no no no! 😅 It's just the way the |
Wdyt about having by default or using an option, a way to make the PR not failing if the resource is (temporarily?) not accessible? |
Hi, I have the same problem. |
Has this issue been fixed? I had to disable this GH workflow in my repos, and I'd like to re-enable them |
When we use
JasonEtco/is-sponsor-label-action
, we get this error:https://github.com/remirror/remirror/pull/1210/checks?check_run_id=3511169860
This action works pretty well the whole time and starts to show this error since yesterday.
The text was updated successfully, but these errors were encountered: