Skip to content

Conversation

@lunny
Copy link
Member

@lunny lunny commented Oct 28, 2025

No description provided.

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Oct 28, 2025
@lunny lunny added the type/refactoring Existing code has been cleaned up. There should be no new functionality. label Oct 28, 2025
@github-actions github-actions bot added modifies/api This PR adds API routes or modifies them modifies/go Pull requests that update Go code labels Oct 28, 2025
return err
}

notify_service.MergePullRequest(baseGitRepo.Ctx, doer, pr)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wait, doesn't this introduce a regression?
Didn't we explicitly change it to this specific context to have a deadline that is different from the request deadline?
With the previous approach, it is merged in the background.
With the new approach, it cannot take longer than the request…

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think they are the same. Both are *services/context.Context.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. modifies/api This PR adds API routes or modifies them modifies/go Pull requests that update Go code type/refactoring Existing code has been cleaned up. There should be no new functionality.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants