Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
The Studio creates a commit every time you save a job, and in many other instances after relatively small change. One thing that happens to me often is I need to change some constant for testing, and then change it back before pushing. Since the job gets saved every time you run, this will generate at least two commits.
We've found you wind up creating upwards of 100 commits per person during a moderately busy day. All those commits in the git revision history make it really hard to follow what actually changed, and to roll back to a previous version.
It would be nice if individual Studio users could squash their commits into a single commit before pushing them up to the remote.
Hello,
Could you please let us know if this jira issue:https://jira.talendforge.org/browse/TUP-15998 is what you are looking for?
Best regards
Sabrina
Doesn't seem related to me.
Hello,
Could you please create a new feature jira issue of DI project on talend bug tracker?
Best rgards
Sabrina
I've asked for a JIRA account. Do you mean this project?
Hello,
Please have a look at my screenshot.
Still no JIRA account, but I think this may work:
We'll try it and I'll report back.
Hello,
Feel free to let us know if the way of 'Change the commit mode to manual' in tac could help.
Best regards
Sabrina
Did anyone ever make a Jira ticket for this? I don't have an account so I can't actually look at those tickets.