Skip to content

Update actions/setup-java action to v3.11.0 (#209) #95

Update actions/setup-java action to v3.11.0 (#209)

Update actions/setup-java action to v3.11.0 (#209) #95

Triggered via push August 8, 2023 09:24
Status Failure
Total duration 2m 12s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

auto-update.yaml

on: push
autoupdate
19s
autoupdate
Fit to window
Zoom out
Zoom in

Annotations

10 errors
autoupdate
Merge conflict error trying to update branch
autoupdate
Caught error running merge, skipping and continuing with remaining PRs
autoupdate
HttpError: Merge conflict
autoupdate
Could not update pull request #225 due to an authorisation error. This is probably because this pull request is from a fork and the current token does not have write access to the forked repository. Error was: Resource not accessible by integration
autoupdate
Could not update pull request #224 due to an authorisation error. This is probably because this pull request is from a fork and the current token does not have write access to the forked repository. Error was: Resource not accessible by integration
autoupdate
Could not update pull request #198 due to an authorisation error. This is probably because this pull request is from a fork and the current token does not have write access to the forked repository. Error was: Resource not accessible by integration
autoupdate
Could not update pull request #222 due to an authorisation error. This is probably because this pull request is from a fork and the current token does not have write access to the forked repository. Error was: Resource not accessible by integration
autoupdate
Could not update pull request #220 due to an authorisation error. This is probably because this pull request is from a fork and the current token does not have write access to the forked repository. Error was: Resource not accessible by integration
autoupdate
Could not update pull request #211 due to an authorisation error. This is probably because this pull request is from a fork and the current token does not have write access to the forked repository. Error was: Resource not accessible by integration
autoupdate
Could not update pull request #207 due to an authorisation error. This is probably because this pull request is from a fork and the current token does not have write access to the forked repository. Error was: Resource not accessible by integration