-
Notifications
You must be signed in to change notification settings - Fork 1
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
Push trigger only works for the multi-branch mode #70
Comments
@joekur the push trigger always requires a branch. In the basic workflow, that branch will be the default, i.e. |
Ahh ok I see. You'd have to rename the existing resource in order for txgh to recognize it as belonging to the develop branch. Specifically I mean you'd have to change the resource's slug, since the branch information is included in each of them. Is it not feasible for you to change the existing resource slugs? In any case, it should be fairly straightforward to not include the branch in the resource slug when using the normal workflow. I thought that was already supported (see |
I'm sure it would be feasible, just not really ideal. On the other hand, I wonder if just using the tx client to push and pull would be equivalent if I'm using just the basic mode? |
I guess it wouldn't update the github statuses though |
Exactly, you'd get all the benefits except github statuses. |
Can you clarify if this was intended, or if I'm missing something? The push trigger endpoint expects a
branch
param, and then it creates a resource tagged with the branch name, even though the project is configured to use the basic workflow.For context, I am not using multi-branch because my understanding is that it will create a resource any time someone pushes a new branch to github. I'm not sure I like the idea that if someone is starting a WIP feature, and they add a translation file that may not yet be finalized, that it ends up immediately in transifex. Thus our flow for now is that nothing gets translated until it's in master.
The text was updated successfully, but these errors were encountered: