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
The PRs are no longer being autolabeled by the probot autolabeler.
It seems for us that the last time labels were applied was about 12 days ago. I tried applying a PR in my local fork, where I have full control over the access rights of probot, but labels were not added there either when previously they were.
Additionally, I checked the apache spark repo and it appears that the last time their probot labeler ran was maybe 10 days ago; At least, that's the oldest age of an open PR I could find that looked to be previously naturally labeled.
This makes me think something happened to the probot labeler. I'm going to open up an issue in the probot autolabeler repo to see if there's something that changed on its end (possibly an npm dependency or something chaged?).
The text was updated successfully, but these errors were encountered:
This is closed. In my the above linked issue, Github user [at]mithro said that they were not able to upgrade the bot to use the new API. I've opened a new issue to upgrade. #1583
The PRs are no longer being autolabeled by the probot autolabeler.
It seems for us that the last time labels were applied was about 12 days ago. I tried applying a PR in my local fork, where I have full control over the access rights of probot, but labels were not added there either when previously they were.
Additionally, I checked the apache spark repo and it appears that the last time their probot labeler ran was maybe 10 days ago; At least, that's the oldest age of an open PR I could find that looked to be previously naturally labeled.
This makes me think something happened to the probot labeler. I'm going to open up an issue in the probot autolabeler repo to see if there's something that changed on its end (possibly an npm dependency or something chaged?).
The text was updated successfully, but these errors were encountered: