How to debug commit errors?

[juliancoffee]

So, because we couldn't make the Codeberg instance work with automated pull requests and all, we're doing everything by ourselves, our procedure is just once a week or so (before our release), manually going through all these buttons from commits, to updates, etc, to locking the repo to avoid Weblate self-inflicted git conflicts (which still sometimes happen for some reason) (because of formatting?).

(Anyway, not really related, more for the context)

Now, to the task at hand - during one of these runs, we got an error for commits (I can't provide if there was an exact error right now, cause I wasn't the one who ran it).
The merge worked in the end, but these "units skipped" still remain, and it's unclear which units are erroneous and why.

I tried to check Repository Changes, but it doesn't seem to show anything suspicious.
Do you have any idea?

I tried running our checks by cloning the Weblate repository using API token access (see #18256), and our tests seem to pass (if I disable our LFS check).

UPD: yes, I just realised that as these units weren't committed, we don't see them in the repository

[pratikrath126]

Hey! For debugging commit errors in Weblate, here are a few practical steps:

• Check the Weblate server logs. Look for error traces around the time of the commit; they often show which units failed and why (e.g., validation errors like mismatched placeholders, format strings, or read-only files).

• • In the Weblate UI, go to the component’s Manage section and look for a Failed or Skip list. It usually displays units that were skipped during commit, along with reasons.
• • Try running a manual commit via the Weblate management command () for that component to see detailed output.
• • Ensure your API token has scope (full control of private repositories if needed) and that the push URL is correct.
• • If you use any quality checks or fill‑required‑source‑strings, they can cause skips; you can temporarily disable them to isolate the issue.
    Hey! For debugging commit errors in Weblate:

• Check the Weblate server logs for error traces around commit time; they often indicate which units failed and why (validation errors like placeholder mismatches, format strings, or read-only files).

• • In the UI, go to the component's Manage section and look for a Failed or Skip list; it shows skipped units with reasons.
• • Run a manual commit via the Weblate management command (weblate commit) for that component to see detailed output.
• • Ensure your API token has repo scope and the push URL is correct.
• • Quality checks (fill-required-source-strings, etc.) can cause skips; temporarily disable to isolate.

• Once you identify problematic units, fix translations and re-commit. Hope this helps!nce you identify the problematic units, you can fix the translations (e.g., adjust placeholders) and re‑commit. Hope that helps you track down the culprit!

[nijel]

You can find affected strings using the search is:pending. The history of each string should show the actual error.

[juliancoffee]

Thank you, that works and also shows failed checks!