Is there a way to limit the # of auto commits that Talend is making to Git, or disable auto-commit altogether?
It appears Talend is doing a commit on every save, which means that the git logs become too cumbersome to determine what's changed. Ideally, I'd be prompted to do a commit on a save, or before existing the application with a prompt to enter a commit message.
@nickheidke,you connect to local from Git repository and you can push the code which you want have in GIt,since from local untill you push it will not commit to GIT.
While it's true that I control when I "push" to the remote repository, Talend appears to be "commit"-ing to my local repository very frequently. Here's a snippet of the commit logs, for instance.
@nickheidke, You can set to Unlock Item to commit for the GIT project in TAC.
@nickheidke,did it help you?
Could you please clarify in which Talend version/edition you are?
Are you able to set to Unlock Item to commit for the GIT project in TAC?
We're using Integration Cloud, not TAC.
Unless I'm mistaken, I haven't seen any settings whatsoever for Git Projects in TIC, other than of-course the repository address and permissions
It looks like a new feature in TIC. With your subscription solution, could you please create a new case on talend support portal? In this way, our colleagues from support team will check it to see if there is a new feature/work item in TIC and then create a jira issue for you.
Sorry for my late reply everyone. This is the response I got from official support about the commit messages:
"The target release for those good features will be added is 7.2.1 so it will definitely getting better to reduce number of commit to Git server. However, R&D hasn't decided which team should develop this, either studio or from TMC. Manual commit and unlock to commit will dramatically get less interaction to Git. I hope this will be handled by TMC team so customer doesn't need to upgrade product."
Additional reference. A jira ticket created on request by another Talend user, set to priority Low:
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Part 2 of a series on Context Variables
Learn how to do cool things with Context Variables
Find out how to migrate from one database to another using the Dynamic schema