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

github: Fix weblate action's rights, and update generated code. #1262

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

alexmv
Copy link
Contributor

@alexmv alexmv commented Jan 8, 2025

This replaces #1192, with the branch pushed to zulip/zulip-flutter so that it can possibly be tested before merging.

@alexmv alexmv force-pushed the action-rights-generated branch 10 times, most recently from 5b163dd to 6264d21 Compare January 13, 2025 19:25
@alexmv alexmv force-pushed the action-rights-generated branch from 6264d21 to 7dff110 Compare January 13, 2025 20:51
Comment on lines -16 to +27
git merge --ff-only weblate/main
GIT_COMMITTER_NAME="Hosted Weblate" GIT_COMMITTER_EMAIL="[email protected]" \
git cherry-pick weblate/main ^HEAD
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm I guess there's a race where if origin/main just got updated and Weblate hasn't taken that update yet, the merge --ff-only will fail.

How about reset --hard? Then the PR's base will be slightly behind the tip, but that's normal. We'll rebase it forward as part of merge like we do for many other PRs.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah I see, this change is part of the "run on this PR" don't-merge commit. Never mind, then.

(There still is that race, but it's unlikely.)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One option is we can git reset --hard weblate/main and let the PR potentially be behind main if weblate is lagging. Which means one might get a PR with "cannot merge" rather than the failure one gets with git merge --ff-only, which is that the whole action fails.

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

Successfully merging this pull request may close these issues.

2 participants