Assigned
Status Update
Comments
lu...@gmail.com <lu...@gmail.com> #2
It looks like this Change is associated with changes on the workflow: GitHub refuses the push because of the missing workflow scope.
replication_log.2021-07-20.gz:[2021-07-20 11:28:46,848] Failed replicate of refs/changes/94/520994/2 tohttps://github.com/cue-lang/cue.git , reason: refusing to allow an OAuth App to create or update workflow `.github/workflows/new_version_triggers.yml` without `workflow` scope [CONTEXT PLUGIN="gerrit" PLUGIN="replication" project="cue-lang/cue" pushOneId="6dd9e878" ]
replication_log.2021-07-20.gz:[2021-07-20 11:28:46,848] Failed replicate of refs/changes/94/520994/2 to
pa...@myitcv.org.uk <pa...@myitcv.org.uk> #3
Thanks. That's very interesting. Must have been the case that I never manually pushed https://review.gerrithub.io/c/cue-lang/cue/+/520792 after submitting it.
Please feel free to close this on the basis it's the same underlying issue as the scope change, which is close to release.
Please feel free to close this on the basis it's the same underlying issue as the scope change, which is close to release.
ek...@google.com <ek...@google.com> #4
[Empty comment from Monorail migration]
ek...@google.com <ek...@google.com> #5
[Monorail components: Hosting>gerrithub]
is...@google.com <is...@google.com> #6
Edits were made to reflect the following in Monorail: auto-CCs.
Description
GerritHub/GitHub username:
myitcv
GerritHub/GitHub projects names:
Full URL exhibiting the problem:
Expected behavior:
Expected the submitted CL to mirror to GitHub.
Observed behavior:
It did not mirror.
Timestamp when the error occurred (include timezone):
12:28 UTC+1 (the time of the submit).
Has this worked before? If yes, when?
Yes, for a number of other non-workflow related CLs. We are aware of issues related to commits that require the workflow auth scope (https://bugs.chromium.org/p/gerrit/issues/detail?id=14533 ), but believe this change is unrelated to that.
Note that for this particular CL, I ended up manually mirroring to GitHub ~10 minutes later. But suspect there will be logs/similar in the interim that show what the problem was?
If applicable: screenshot of erroneous UI element:
n/a
If applicable: JavaScript console log (chrome: F12 > Console):
n/a
If applicable: Browser (name, version, operating system)
n/a
If using git command-line: output of "which git && git --version"
n/a