You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently updated from Weblate 5.6 -> 5.9.2.1 via Docker. With the update, the "Squash Git Commits" add-on stopped working. I noticed there was a change between versions where you can now install add-ons at the project level, so I removed it from the component and re-installed it at the project. Unfortunately, the issue still persists where a single author making changes to two or more files is being added as individual commits.
I've searched for similar filed issues in this repository.
Steps to reproduce the behavior
Have a single component configured (mine is called "dummy")
Use the add-on "Component discovery" and configure it. I'm currently pulling in about 950~ components with 450k total managed strings
Enable the "Squash Git Commits" add-on at the project level
Commit squashing: Author
Append trailers to squashed commit messages: Checked
Commit message: Blank
Have a user make a commit in two or more different components
In Manage > Repository Maintenance, manually click "Commit" and "Push" to bypass the scheduled 1 hour push
Two individual commits are created
I've checked the add-on's logs (with the "Manage logs" button on the add-on) and there is no activity.
Expected behavior
No response
Screenshots
All of these commits should have been squashed into one commit. They were committed and pushed at the same time by Weblate's scheduling. There are multiple changes performed on a single component, but all components changed by the author should have been squashed into a single commit. See the "Additional context" section for a link to this repository.
Exception traceback
There are no exceptions or errors in the logs when the sync occurs. I check this with `docker logs weblate -f`.
security.W012: SESSION_COOKIE_SECURE is not set to True.
weblate.I021: Error collection is not set up, it is highly recommended for production use
weblate.I028: Message about manual backups
Additional context
One thing I've noticed is that in my "dummy" component (where the Component discovery add-on is listed), if I make an edit here and then in another file, those are getting squashed. But if I pick other components, they are all individual.
Here's the commit history for the repo Weblate is publishing to:
Describe the issue
I recently updated from Weblate 5.6 -> 5.9.2.1 via Docker. With the update, the "Squash Git Commits" add-on stopped working. I noticed there was a change between versions where you can now install add-ons at the project level, so I removed it from the component and re-installed it at the project. Unfortunately, the issue still persists where a single author making changes to two or more files is being added as individual commits.
I already tried
Steps to reproduce the behavior
I've checked the add-on's logs (with the "Manage logs" button on the add-on) and there is no activity.
Expected behavior
No response
Screenshots
All of these commits should have been squashed into one commit. They were committed and pushed at the same time by Weblate's scheduling. There are multiple changes performed on a single component, but all components changed by the author should have been squashed into a single commit. See the "Additional context" section for a link to this repository.
Exception traceback
How do you run Weblate?
Docker container
Weblate versions
Weblate deploy checks
docker compose exec --user weblate weblate weblate check --deploy System check identified no issues (39 silenced).
Silenced checks:
Additional context
One thing I've noticed is that in my "dummy" component (where the Component discovery add-on is listed), if I make an edit here and then in another file, those are getting squashed. But if I pick other components, they are all individual.
Here's the commit history for the repo Weblate is publishing to:
https://github.com/dqx-translation-project/dqx_translations/commits/main/
Thanks for this wonderful product.
The text was updated successfully, but these errors were encountered: