Skip to content

Conversation

kemzeb
Copy link
Member

@kemzeb kemzeb commented Sep 14, 2025

Fix #35463.

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Sep 14, 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 Sep 14, 2025
@kemzeb
Copy link
Member Author

kemzeb commented Sep 14, 2025

The logic has been implemented, but for tests I need to figure out how to work with the git database in the test environment.

Did not see issues when manual-testing the following:

  • Merge with delete branch when merge repo setting is set
  • Merge with delete branch when merge API form field is set
  • Merge without either fields set

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Merging a PR via the API does not honor the Delete pull request branch after merge by default setting
2 participants