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

How can i change the component which was fork from the existing component to a independent git repo or branch ? #4236

Closed
deboyblog opened this issue Jul 31, 2020 · 8 comments
Labels
question This is more a question for the support than an issue.

Comments

@deboyblog
Copy link

deboyblog commented Jul 31, 2020

Describe the issue

There is a component that already exists name a-component
then i create a new component form that existing component name b-component
when b-component have some original words update and new key-value added, and i don't want to sync to the a-component git repo.
but when i clone the a-component repo, it's always the lastest update on b-component.
Q1: how can i create the different branch to contain b-component in a-component git repo?
Q2: when i using this api to get the component info, b-component without git_export, there is noway to clone b-component repo, and there is no field to told me b-component is connect to a-component


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@deboyblog deboyblog added the question This is more a question for the support than an issue. label Jul 31, 2020
@github-actions
Copy link

This issue looks like a support question. We try to answer these reasonably fast, but in case you are looking for faster resolution, please consider purchasing support subscription and make Weblate stronger.

@deboyblog deboyblog changed the title How can i change the component which was fork from the existing component to a independent git repo? How can i change the component which was fork from the existing component to a independent git repo or branch ? Jul 31, 2020
@nijel
Copy link
Member

nijel commented Aug 1, 2020

Maybe I'm missing something, but in case you have different branches, the components won't share the repository. How exactly did you create the b-component? "From existing component" chooses different files from the same component, sharing the underlying repo, there is also "Additional branch" where you can choose different branch from the repo (but it has to already exist). See also https://docs.weblate.org/en/latest/admin/projects.html#adding-translation-projects-and-components

@deboyblog
Copy link
Author

My wablate version is 4.1.1.
I didn't see "Additional branch" option when I create a new component, which step can I see this option?
image

@nijel
Copy link
Member

nijel commented Aug 2, 2020

The option will be there only if there is a repository which has more branches.

@deboyblog
Copy link
Author

deboyblog commented Aug 3, 2020

The option will be there only if there is a repository which has more branches.

how can I cretae more branch if I use the wablate default repository?
I found that I couldn't push it after I cloned my weblate component repo with username and password like git clone https://username:password@translate.xxx.com
when I tried to push the new branch to remote there was an error code 403

@nijel
Copy link
Member

nijel commented Aug 7, 2020

In case you did not used remote repository, just create again new component from scratch. Playing with branches doesn't bring any benefits in this case.

@deboyblog
Copy link
Author

I changed to use the remote repository by connect to gitlab, it's solved my problem.
Thank you for your patient reply.

@github-actions
Copy link

github-actions bot commented Aug 7, 2020

The issue you have reported seems to be resolved now.

  • In case you see a similar problem, please open a separate issue.
  • If you are happy with the outcome, consider supporting Weblate by donating.

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