Skip to content

Conversation

zeripath
Copy link
Contributor

Backport #22535

The update by rebase code reuses the merge code but shortcircuits and pushes back up to the head. However, it doesn't set the correct pushing environment - and just uses the same environment as the base repo. This leads to the push update failing and thence the PR becomes out-of-sync with the head.

This PR fixes this and adjusts the trace logging elsewhere to help make this clearer.

Fix #18802

Signed-off-by: Andrew Thornton art27@cantab.net

…o-gitea#22535)

Backport go-gitea#22535

The update by rebase code reuses the merge code but shortcircuits and
pushes back up to the head. However, it doesn't set the correct pushing
environment - and just uses the same environment as the base repo. This
leads to the push update failing and thence the PR becomes out-of-sync
with the head.

This PR fixes this and adjusts the trace logging elsewhere to help make
this clearer.

Fix go-gitea#18802

Signed-off-by: Andrew Thornton <art27@cantab.net>
@zeripath zeripath added this to the 1.18.2 milestone Jan 19, 2023
@GiteaBot GiteaBot added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Jan 19, 2023
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Jan 19, 2023
Signed-off-by: Andrew Thornton <art27@cantab.net>
@zeripath zeripath force-pushed the backport-22535-v1.18 branch from af50294 to 2798b89 Compare January 19, 2023 21:39
@zeripath
Copy link
Contributor Author

I've force pushed and updated the 1.18.2 changelog at the same time

Signed-off-by: Andrew Thornton <art27@cantab.net>
@techknowlogick techknowlogick merged commit 3c531d3 into go-gitea:release/v1.18 Jan 19, 2023
@zeripath zeripath deleted the backport-22535-v1.18 branch January 19, 2023 22:52
@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. type/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants