Open mikaelarguedas opened 3 years ago
Why is None
appended to the end of the git push command?
cmdline: git push --force upstream_pr ros/rolling/ubuntu/focal:ros/rolling/ubuntu/focalNone
I suspect this is a misleading print as we use the exact same string before and after the :
Maybe something changed in the permissions / token of the osrf-docker-builder
user? I do not have access to that account so am unable to look further into it.
Maybe @tfoote or @nuclearsandwich would know more ?
The last successful push was on April 28th
The first failed push was on May 5th
My best guess is that the keys used to push might have been invalidated? Possibly relating to codecov security @nuclearsandwich I see an attached specific key instead of leveraging single use github generated keys which I think can work for our use case: https://docs.github.com/en/actions/reference/authentication-in-a-workflow
@tfoote @nuclearsandwich Any news on this topic ? I would love to stop opening these PRs by hand ^^'
@tfoote @nuclearsandwich @sloretz with some current template changes:
we'll need this issue resolved so we can finally address:
Any updates?
I think our GITHUBTOKEN
that was Personal Access Tokens from @osrf-docker-builder would need to be reissued.
https://github.com/osrf/docker_images/settings/secrets/actions
Alternatively, between the time that we first added our bot, it seems GitHub Actions marketplace supports this integration:
https://github.com/marketplace/actions/create-pull-request
@mikaelarguedas , it seems that the setting to allow GitHub Actions to create pull requests is already enabled for osrf/docker_images
. I think we could also use this to open PR from our org's fork of docker-library/official-images
:
There also seems to be a caveat on using automated PR to trigger automated workflows:
Note: If you want pull requests created by this action to trigger an on: push or on: pull_request workflow then you cannot use the default GITHUB_TOKEN. See the documentation here for workarounds.
Last night the foxy and rolling images were out of date and CI tried to creat PRs to update them but failed with:
@ruffsl FYI