@prabirshrestha The idea of Pull Requests are so that physical programmers can review the code before merging it, so I am unsure the use of this feature, just because something complies does not mean it doesn't contain logic issues, or vulnerabilities which a programmer would pick up during review.

Personally I do not see the need for this feature, PR's should be reviewed and this removes the idea of PR's.

At work we have 300+ devs working on the same repro and I can't imagine how one would be able to live without this feature as there are high chances of having merge conflicts. There are settings one can apply to project such that if someone comments on autocomplete PRs, projects can set settings such that the same folks need to review before it can be signed off.

For now I'm primarily using onedev for personal where I'm only the dev so it makes sense for me to set auto complete to most PRs and then checkin if my CI passes.

State changed as code fixing the issue is committed (d35f84ef)

State changed as build OD-5739 is successful

@robin If a squash merge strategy is chosen that uses the PR title and description as commit message AND the project has conventional commits enabled then it might be a good idea to check the PR title and description so that auto merge actually succeeds.

@jbauer I filed a bug for this: OD-2203