Hi All,

We have successfully integrated GitHub with PAW and are able to use its capabilities. However, we are facing an issue while pushing objects to an existing branch.

When pushing to a new branch, everything works as expected-the selected objects are pushed correctly. However, when pushing to an existing branch, the previously existing objects in that branch are getting replaced. Ideally, it should only update the modified objects or add new ones, without removing the existing files.

This limitation is restricting us from fully utilizing this capability.

To explain with an example:
If an existing branch contains 10 TI processes, and I update only 2 TIs in TM1, pushing these changes should update only those 2 files while retaining all 10 files in the branch. However, currently, the branch ends up containing only those 2 files, replacing the original 10 files.

Please let me know if anyone has insights into this issue or has encountered a similar situation.

Thanks,
Ajit Kumar

Hi Ajit,

You are correct.

You can either push all to keep everything in Git but you cannot select some of changes in given objects.

Any changes to any objects would be pushed, or push selected objects but the rest won't be in Git.

We have plans to implement selective push later this year.

Best regards,

Hi All,

We have successfully integrated GitHub with PAW and are able to use its capabilities. However, we are facing an issue while pushing objects to an existing branch.

When pushing to a new branch, everything works as expected-the selected objects are pushed correctly. However, when pushing to an existing branch, the previously existing objects in that branch are getting replaced. Ideally, it should only update the modified objects or add new ones, without removing the existing files.

This limitation is restricting us from fully utilizing this capability.

To explain with an example:
If an existing branch contains 10 TI processes, and I update only 2 TIs in TM1, pushing these changes should update only those 2 files while retaining all 10 files in the branch. However, currently, the branch ends up containing only those 2 files, replacing the original 10 files.

Please let me know if anyone has insights into this issue or has encountered a similar situation.

Thanks,
Ajit Kumar

Hi Ajit,

You are correct.

You can either push all to keep everything in Git but you cannot select some of changes in given objects.

Any changes to any objects would be pushed, or push selected objects but the rest won't be in Git.

We have plans to implement selective push later this year.

Best regards,

Hi All,

We have successfully integrated GitHub with PAW and are able to use its capabilities. However, we are facing an issue while pushing objects to an existing branch.

When pushing to a new branch, everything works as expected-the selected objects are pushed correctly. However, when pushing to an existing branch, the previously existing objects in that branch are getting replaced. Ideally, it should only update the modified objects or add new ones, without removing the existing files.

This limitation is restricting us from fully utilizing this capability.

To explain with an example:
If an existing branch contains 10 TI processes, and I update only 2 TIs in TM1, pushing these changes should update only those 2 files while retaining all 10 files in the branch. However, currently, the branch ends up containing only those 2 files, replacing the original 10 files.

Please let me know if anyone has insights into this issue or has encountered a similar situation.

Thanks,
Ajit Kumar

Hi Svetlana,

Thanks for the update.

Could you please share the expected timeline for this? Also, in which version will this enhancement be supported?

Thanks,
Ajit

Hi Ajit,

You are correct.

You can either push all to keep everything in Git but you cannot select some of changes in given objects.

Any changes to any objects would be pushed, or push selected objects but the rest won't be in Git.

We have plans to implement selective push later this year.

Best regards,

Hi All,

We have successfully integrated GitHub with PAW and are able to use its capabilities. However, we are facing an issue while pushing objects to an existing branch.

When pushing to a new branch, everything works as expected-the selected objects are pushed correctly. However, when pushing to an existing branch, the previously existing objects in that branch are getting replaced. Ideally, it should only update the modified objects or add new ones, without removing the existing files.

This limitation is restricting us from fully utilizing this capability.

To explain with an example:
If an existing branch contains 10 TI processes, and I update only 2 TIs in TM1, pushing these changes should update only those 2 files while retaining all 10 files in the branch. However, currently, the branch ends up containing only those 2 files, replacing the original 10 files.

Please let me know if anyone has insights into this issue or has encountered a similar situation.

Thanks,
Ajit Kumar

Hi Ajit,

Expecting 12.6 or later,

Best regards,

Hi Svetlana,

Thanks for the update.

Could you please share the expected timeline for this? Also, in which version will this enhancement be supported?

Thanks,
Ajit

Hi Ajit,

You are correct.

You can either push all to keep everything in Git but you cannot select some of changes in given objects.

Any changes to any objects would be pushed, or push selected objects but the rest won't be in Git.

We have plans to implement selective push later this year.

Best regards,

Hi All,

We have successfully integrated GitHub with PAW and are able to use its capabilities. However, we are facing an issue while pushing objects to an existing branch.

When pushing to a new branch, everything works as expected-the selected objects are pushed correctly. However, when pushing to an existing branch, the previously existing objects in that branch are getting replaced. Ideally, it should only update the modified objects or add new ones, without removing the existing files.

This limitation is restricting us from fully utilizing this capability.

To explain with an example:
If an existing branch contains 10 TI processes, and I update only 2 TIs in TM1, pushing these changes should update only those 2 files while retaining all 10 files in the branch. However, currently, the branch ends up containing only those 2 files, replacing the original 10 files.

Please let me know if anyone has insights into this issue or has encountered a similar situation.

Thanks,
Ajit Kumar

Hi Svetlana,

Is that tied to v11 or v12 only?  Any expectation on the PAW version as well?

Hi Ajit,

Expecting 12.6 or later,

Best regards,

Hi Svetlana,

Thanks for the update.

Could you please share the expected timeline for this? Also, in which version will this enhancement be supported?

Thanks,
Ajit

Hi Ajit,

You are correct.

You can either push all to keep everything in Git but you cannot select some of changes in given objects.

Any changes to any objects would be pushed, or push selected objects but the rest won't be in Git.

We have plans to implement selective push later this year.

Best regards,

Hi All,

We have successfully integrated GitHub with PAW and are able to use its capabilities. However, we are facing an issue while pushing objects to an existing branch.

When pushing to a new branch, everything works as expected-the selected objects are pushed correctly. However, when pushing to an existing branch, the previously existing objects in that branch are getting replaced. Ideally, it should only update the modified objects or add new ones, without removing the existing files.

This limitation is restricting us from fully utilizing this capability.

To explain with an example:
If an existing branch contains 10 TI processes, and I update only 2 TIs in TM1, pushing these changes should update only those 2 files while retaining all 10 files in the branch. However, currently, the branch ends up containing only those 2 files, replacing the original 10 files.

Please let me know if anyone has insights into this issue or has encountered a similar situation.

Thanks,
Ajit Kumar