weblate-one weblate-second # Merge QA_4_7 branch: git checkout QA_4_7 git merge weblate-one/QA_4_7 ... # Resolve conflicts git commit # Merge master branch: git checkout master git merge weblates-second/master repository). In case the Push branch is not set, the project is forked and changes pushed through a fork. In case it is set, changes are pushed to the upstream repository and chosen branch. For smaller deployments Weblate tries to detect Subversion repository layout automatically - it supports both direct URLs for branch or repositories with standard layout (branches/, tags/ and trunk/). More info about this is to be

update weblate-one weblate-second # Merge QA_4_7 branch: git checkout QA_4_7 git merge weblate-one/QA_4_7 ... # Resolve conflicts git commit # Merge main branch: git checkout main git merge weblates-second/main once). In case the Push branch is not set, the project is forked and changes pushed through a fork. In case it is set, changes are pushed to the upstream repository and chosen branch. For smaller deployments Weblate tries to detect Subversion repository layout automatically - it supports both direct URLs for branch or repositories with standard layout (branches/, tags/ and trunk/). More info about this is to be

weblate-one weblate-second # Merge QA_4_7 branch: git checkout QA_4_7 git merge weblate-one/QA_4_7 ... # Resolve conflicts git commit # Merge master branch: git checkout master git merge weblates-second/master repository). In case the Push branch is not set, the project is forked and changes pushed through a fork. In case it is set, changes are pushed to the upstream repository and chosen branch. For smaller deployments Weblate tries to detect Subversion repository layout automatically - it supports both direct URLs for branch or repositories with standard layout (branches/, tags/ and trunk/). More info about this is to be

update weblate-one weblate-second # Merge QA_4_7 branch: git checkout QA_4_7 git merge weblate-one/QA_4_7 ... # Resolve conflicts git commit # Merge main branch: git checkout main git merge weblates-second/main once). In case the Push branch is not set, the project is forked and changes pushed through a fork. In case it is set, changes are pushed to the upstream repository and chosen branch. For smaller deployments Weblate tries to detect Subversion repository layout automatically - it supports both direct URLs for branch or repositories with standard layout (branches/, tags/ and trunk/). More info about this is to be

update weblate-one weblate-second # Merge QA_4_7 branch: git checkout QA_4_7 git merge weblate-one/QA_4_7 ... # Resolve conflicts git commit # Merge main branch: git checkout main git merge weblates-second/main once). In case the Push branch is not set, the project is forked and changes pushed through a fork. In case it is set, changes are pushed to the upstream repository and chosen branch. For smaller deployments Weblate tries to detect Subversion repository layout automatically - it supports both direct URLs for branch or repositories with standard layout (branches/, tags/ and trunk/). More info about this is to be

weblate-one weblate-second # Merge QA_4_7 branch: git checkout QA_4_7 git merge weblate-one/QA_4_7 ... # Resolve conflicts git commit # Merge master branch: git checkout master git merge weblates-second/master repository). In case the Push branch is not set, the project is forked and changes pushed through a fork. In case it is set, changes are pushed to the upstream repository and chosen branch. For smaller deployments Weblate tries to detect Subversion repository layout automatically - it supports both direct URLs for branch or repositories with standard layout (branches/, tags/ and trunk/). More info about this is to be

weblate-one weblate-second # Merge QA_4_7 branch: git checkout QA_4_7 git merge weblate-one/QA_4_7 ... # Resolve conflicts git commit # Merge master branch: git checkout master git merge weblates-second/master repository). In case the Push branch is not set, the project is forked and changes pushed through a fork. In case it is set, changes are pushed to the upstream repository and chosen branch. For smaller deployments Weblate tries to detect Subversion repository layout automatically - it supports both direct URLs for branch or repositories with standard layout (branches/, tags/ and trunk/). More info about this is to be

update weblate-one weblate-second # Merge QA_4_7 branch: git checkout QA_4_7 git merge weblate-one/QA_4_7 ... # Resolve conflicts git commit # Merge main branch: git checkout main git merge weblates-second/main once). In case the Push branch is not set, the project is forked and changes pushed through a fork. In case it is set, changes are pushed to the upstream repository and chosen branch. For smaller deployments Weblate tries to detect Subversion repository layout automatically - it supports both direct URLs for branch or repositories with standard layout (branches/, tags/ and trunk/). More info about this is to be

weblate-one weblate-second # Merge QA_4_7 branch: git checkout QA_4_7 git merge weblate-one/QA_4_7 ... # Resolve conflicts git commit # Merge master branch: git checkout master git merge weblates-second/master repository). In case the Push branch is not set, the project is forked and changes pushed through a fork. In case it is set, changes are pushed to the upstream repository and chosen branch. For smaller deployments Weblate tries to detect Subversion repository layout automatically - it supports both direct URLs for branch or repositories with standard layout (branches/, tags/ and trunk/). More info about this is to be

weblate-one weblate-second # Merge QA_4_7 branch: git checkout QA_4_7 git merge weblate-one/QA_4_7 ... # Resolve conflicts git commit # Merge master branch: git checkout master git merge weblates-second/master repository). In case the Push branch is not set, the project is forked and changes pushed through a fork. In case it is set, changes are pushed to the upstream repository and chosen branch. For smaller deployments Weblate tries to detect Subversion repository layout automatically - it supports both direct URLs for branch or repositories with standard layout (branches/, tags/ and trunk/). More info about this is to be