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

Q: Is it okay to have few projects in single git repo? #6836

Closed
2 tasks done
Belorus opened this issue Nov 20, 2021 · 3 comments
Closed
2 tasks done

Q: Is it okay to have few projects in single git repo? #6836

Belorus opened this issue Nov 20, 2021 · 3 comments
Labels
question This is more a question for the support than an issue.

Comments

@Belorus
Copy link

Belorus commented Nov 20, 2021

Describe the issue

Subj :)

I have multiple projects with 3 components each.

Components reflect git branches (dev/release/prod).
Projects sit in same git repo, and structure is simple (same for each branch):

/project1/en_US.json
/project1/ja_JP.json
/project2/en_US.json
/project2/ja_JP.json
/project3/en_US.json
/project3/ja_JP.json

Branches (components) are merged dev -> release -> prod to follow our app git branching approach.

I have lots issues with git conflicts, and got a feeling that projects in same repo might be a bad idea. Could you please share best practices?

In documentation there is a phrase that same repo can be shared between components, but can it be shared between components AND projects?

I already tried

  • I've read and searched the documentation.
  • I've searched for similar issues in this repository.

Steps to reproduce the behavior

  1. Go to '...'
  2. Scroll down to '...'
  3. Click on '...'
  4. See error

Expected behavior

No response

Screenshots

No response

Exception traceback

No response

How do you run Weblate?

Docker container

Weblate versions

4.8.1

Weblate deploy checks

No response

Additional context

No response

@Belorus Belorus added the question This is more a question for the support than an issue. label Nov 20, 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!

@nijel
Copy link
Member

nijel commented Nov 20, 2021

If your translations are done in Weblate into multiple branches, it is recommended to avoid merging translations in git and use a merge strategy that prefers branch translations when merging. See https://docs.weblate.org/en/latest/faq.html#how-do-i-translate-several-branches-at-once (or https://github.com/phpmyadmin/phpmyadmin/wiki/Git#merging-translations).

@Belorus Belorus closed this as completed Nov 20, 2021
@github-actions
Copy link

The issue you have reported is now resolved. If you don’t feel it’s right, please follow its labels to get a clue for further steps.

  • 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
question This is more a question for the support than an issue.
Projects
None yet
Development

No branches or pull requests

2 participants