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

Improve i18n ci #10209

Merged
merged 1 commit into from
Feb 14, 2025
Merged

Improve i18n ci #10209

merged 1 commit into from
Feb 14, 2025

Conversation

FelixMalfait
Copy link
Member

No description provided.

@FelixMalfait FelixMalfait merged commit f45f7c2 into main Feb 14, 2025
10 checks passed
@FelixMalfait FelixMalfait deleted the i18n-ci-2 branch February 14, 2025 08:56
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

PR Summary

This PR modifies the i18n translation workflow to streamline the branch setup process for handling translations in the Twenty project.

  • Simplified i18n branch setup in .github/workflows/i18n-push.yaml using a more concise two-command approach with fallback handling
  • Added error tolerance for missing remote i18n branch with git fetch origin i18n || true
  • Introduced unified branch checkout/creation with git checkout -B i18n origin/i18n || git checkout -b i18n

1 file(s) reviewed, 2 comment(s)
Edit PR Review Bot Settings | Greptile

Comment on lines +28 to +29
git fetch origin i18n || true
git checkout -B i18n origin/i18n || git checkout -b i18n
Copy link
Contributor

Choose a reason for hiding this comment

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

logic: This new approach could silently fail if the remote branch exists but is inaccessible. Consider adding error handling or logging.

git merge origin/main
fi
git fetch origin i18n || true
git checkout -B i18n origin/i18n || git checkout -b i18n
Copy link
Contributor

Choose a reason for hiding this comment

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

logic: The new implementation no longer merges with main, which could lead to conflicts if the i18n branch falls behind.

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.

1 participant