Tatsh / deltona / 25648125038 / 4

100%

master: 100%

push

github

git: suppress traceback on unmergeable PRs outside debug

When `merge-dependabot-prs` or `merge-pre-commit-ci-prs` runs without
`-d`/`--debug`, a single failed merge inside `process_pull` previously
emitted a full Python traceback via `log.exception`, even though the
outer `_run_bot_merge_with_retry` loop will retry the affected
repository on the next pass. The noisy stderr output made transient
GitHub API hiccups look like crashes.

Branch on `log.isEnabledFor(logging.DEBUG)` in the
`except github.GithubException:` block: in debug mode keep
`log.exception(...)` so the traceback survives for diagnosis;
otherwise emit a one-line `log.warning(...)` that names the PR and
repo and notes that the merge will be retried. The recreate-comment
post and `return False` (which keeps the repo in
`BotMergeError.remaining` and therefore in the next retry batch) are
unchanged.

Add `test_merge_dependabot_pull_requests_should_raise_debug` covering
the debug branch (using `caplog.at_level(logging.DEBUG, ...)`) so the
new condition is exercised at 100% coverage. Note the user-facing
behaviour change in `CHANGELOG.md` under `Changed`.

Signed-off-by: Andrew Udvare <audvare@gmail.com>

400 of 400 branches covered (100.0%)

Branch coverage included in aggregate %.

3348 of 3348 relevant lines covered (100.0%)

1.0 hits per line