Skip to content

Update sbt-header to 5.10.0 (#338) #513

Update sbt-header to 5.10.0 (#338)

Update sbt-header to 5.10.0 (#338) #513

Triggered via push June 29, 2023 14:51
Status Success
Total duration 3m 0s
Artifacts
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

autoupdate.yml

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

Annotations

10 errors
autoupdate
Could not update pull request #336 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 #347 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 #346 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 #345 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 #344 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 #343 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 #339 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 #337 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 #334 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 #308 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