Tatsh / wiswa-vcs / 30971165195

100%

push

github

project: tolerate GitLab refusing part of a sync

A `PUT /projects/:id` is validated as a whole, so a single field GitLab
dislikes, such as a `pages_access_level` that conflicts with the
project visibility, discarded the description, topics, and homepage
with it. The resulting BadRequest then propagated out of
sync_github_to_gitlab and aborted the run before branch protection,
tag protection, badges, and housekeeping.

Identify the rejected fields from the error, drop them, and retry the
remaining settings. Both payload shapes GitLab uses are handled: the
humanised attribute prefix and the field-to-errors mapping. A refusal
that names no recognisable setting abandons only the settings update.

Each later GitLab step now logs a 400, 403, 404, or 422 refusal and
continues, matching the per-call tolerance github.py already has.
Anything else, including a 401 or a server error, still aborts. API
failures from either host now print one line instead of a traceback;
pass --debug for the traceback.

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

109 of 109 branches covered (100.0%)

Branch coverage included in aggregate %.

1064 of 1064 relevant lines covered (100.0%)

5.0 hits per line