Talend Studio - Comparing Changes when using Git

[n999]

Hello

We are on a Talend 6.4.1 licence and are using Git for our Source Control.

We check out a local branch from a remote branch and Push local saves/commits to the remote branch.

Talend Studio shows yet-to-be-pushed changes as an asterisk at the top of the repository window, against the whole branch, but, if I wanted to, how do I find out what this commit is and if I want to push or reset?

All IDEs I have worked on allow you to:

1) See which file has changed since the last push.

2) Compare the file to the latest in the remote to see the actual yet-to-be-pushed changes.

Looking at https://help.talend.com/reader/6lpaT_M~MEVrltFQcrPe4g/TXvw6BlVi2o~mbuheN3O5g it says

"In the Repository tree view of Talend Studio, an item with uncommitted changes is preceded by a > symbol."

I can't see this symbol, but it also says "For a Git managed project, information in this section is applicable only when you are working on a remote branch." I find this confusing as when we have worked in a remote branch direct all saves are commits to the remote branch. So is ">" just an indication of an unsaved job?

I also changed a tMap in one job and then tried Right-Hand-Click>Compare Job and was able to choose the same job from a list of remote branches to compare against. So I chose the remote version of my local branch, but my change was not picked up by this view....?

Is there any way to 

1) see which file has changed since the last push.

2) Compare the file to the latest in the remote to see the yet-to-be-pushed changes.

This seems to be a basic and essential IDE ability?

Thanks for any advice.

[Anonymous]

Hello,

For a Git managed project, are you working on a remote branch?

Have you already checked this online documentation:

Working with project branches and tags.

Best regards

Sabrina

[n999]

Hello

Yes I have read that.

Those pages are where I saw the "For a Git managed project, information in this section is applicable only when you are working on a remote branch".

I will read them again to see if I have missed anything but my questions still stand.

No we are not working in the remote branch as this is considered bad practise with Git. Git allows you to have a local copy of the repo you save/commit to before pushing to the remote. Working in the remote means your saved commits are pushed automatically meaning you can't test/review your work before adding to the remote.

Thanks

[jdrury]

I'm also curious as to the best practice around this.   I have saved locally, and I see the indication of number of changed files above the tree view, but how can I see what the push is going to push?  Can I selectively push or selectively reset to remote version or is it a all or nothing?

thanks,

Jon

[Anjali3]

Can someone answer the below question?

  I have saved locally, and I see the indication of number of changed files above the tree view, but how can I see what the push is going to push?