Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bulk Edit addon doesn't run automatically on git updates #5524

Closed
1 task done
spacecowboy opened this issue Feb 26, 2021 · 6 comments
Closed
1 task done

Bulk Edit addon doesn't run automatically on git updates #5524

spacecowboy opened this issue Feb 26, 2021 · 6 comments
Assignees
Labels
bug Something is broken.
Milestone

Comments

@spacecowboy
Copy link

spacecowboy commented Feb 26, 2021

Describe the issue

I have setup the Bulk Edit addon to set changelogs as read-only and it is not triggered automatically. I have to manually edit and save the config to make it run on each release.

I already tried

Describe the steps you tried to solve the problem yourself.

  • I've read and searched the docs and did not find the answer there.
    If you didn’t try already, try to search there what you wrote above.

To Reproduce the issue

Steps to reproduce the behavior:

  1. Configure weblate to monitor your gitlab repo
  2. Add bulk edit addon to your app store metadata component
  3. Configure it with custom search key:changelogs, state do not change, and translation flags to add read-only
  4. Add a changelog to the project, a file such as fastlane/metadata/android/en-US/changelogs/99.txt
  5. Push the commit to your project
  6. Go to weblate and manually click Update to ensure it has the commit

Expected behavior

When the new commit is pulled, bulk-edit runs, and the new changelog is marked as read-only in all languages.

What actually happens

bulk-edit doesn't run - and user is forced to open config and save config to make it run - for every release made to the project.

@nijel
Copy link
Member

nijel commented Feb 26, 2021

It is supposed to run on translation files update. What version do you use? There were some changes in signals triggering in 4.5, but I'm not sure it could be related.

@spacecowboy
Copy link
Author

It is supposed to run on translation files update. What version do you use? There were some changes in signals triggering in 4.5, but I'm not sure it could be related.

Whatever version hosted.weblate.org runs.

@nijel
Copy link
Member

nijel commented Feb 27, 2021

Would you mind sharing the component where it happens so that we can take a look?

@nijel nijel added the question This is more a question for the support than an issue. label Feb 27, 2021
@github-actions
Copy link

This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger. In case your question is already answered, making a donation is the right way to say thank you!

@spacecowboy
Copy link
Author

Would you mind sharing the component where it happens so that we can take a look?

Sure, it's https://hosted.weblate.org/projects/feeder/f-droid-and-play-store-metadata/

@nijel nijel added the bug Something is broken. label Mar 1, 2021
@nijel nijel added this to the 4.5.1 milestone Mar 1, 2021
@nijel nijel removed the question This is more a question for the support than an issue. label Mar 1, 2021
@nijel nijel self-assigned this Mar 1, 2021
@nijel nijel closed this as completed in 3b7b73a Mar 1, 2021
@github-actions
Copy link

github-actions bot commented Mar 1, 2021

Thank you for your report, the issue you have reported has just been fixed.

  • In case you see a problem with the fix, please comment on this issue.
  • In case you see a similar problem, please open a separate issue.
  • If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is broken.
Projects
None yet
Development

No branches or pull requests

2 participants