Pulling changes from my repo into Weblate throwing errors

[nnhubbard]

I have pushed some changes from my IDE to my github repo and expected that Weblate would pull those in automatically. It didn't, so I used the "Update" option in Repository Maintenance, but I get this error:

Could not push Cachly/Cachly Translation: To github.com:nnhubbard/cachly-translations.git ! [rejected] main -> main (fetch first) error: failed to push some refs to 'github.com:nnhubbard/cachly-translations.git' hint: Updates were rejected because the remote contains work that you do not hint: have locally. This is usually caused by another repository pushing to hint: the same ref. If you want to integrate the remote changes, use hint: 'git pull' before pushing again. hint: See the 'Note about fast-forwards' in 'git push --help' for details. (1)

What is the correct method for pulling in updated .xliff files into Weblate? What am I missing here?

[nijel]

Automatic updates need to be configured on GitHub, see https://docs.weblate.org/en/latest/admin/continuous.html#automatically-receiving-changes-from-github.

The actual error is from pushing from Weblate and it fails because Weblate repository is behind. Update might trigger pushing when there are pending changes and push on commit is configured.

[nnhubbard]

I have setup automatic updates using webhooks in Github.

Do I need to use the "Update" option in Weblate when I make changes in my IDE strings which then updates my .xliff files on github? Currently I still get this error when trying to push outgoing commits in the repository maintenance section. Same error has before:

Could not push Cachly/Cachly Translation: To github.com:nnhubbard/cachly-translations.git ! [rejected] main -> main (fetch first) error: failed to push some refs to 'github.com:nnhubbard/cachly-translations.git' hint: Updates were rejected because the remote contains work that you do not hint: have locally. This is usually caused by another repository pushing to hint: the same ref. If you want to integrate the remote changes, use hint: 'git pull' before pushing again. hint: See the 'Note about fast-forwards' in 'git push --help' for details. (1)