Planning Analytics

Planning Analytics

Get AI-infused integrated business planning

 View Only
  • 1.  Git Integration With PAW

    Posted 04/02/26 06:15 PM

    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



    ------------------------------
    Ajit Kumar
    ------------------------------


  • 2.  RE: Git Integration With PAW

    Posted 04/06/26 10:28 AM

    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,



    ------------------------------
    Svetlana Pestsova
    IBM Planning Analytics Product Manager
    ------------------------------



  • 3.  RE: Git Integration With PAW

    Posted 04/07/26 03:57 AM

    Hi Ajit, Svetlana,

    Allow me to intervene here briefly, the problem is actually that PAW's so called 'GIT integration' is not really sharing the vision of GIT integration for which it was build into TM1. Instead it is focused on object movement and rather treats GIT as a fancy backup location from which you can restore/pull somewhere else again.

    That said the 'selective push' the TM1 team is looking to implement won't really help you either here, that would presumably intersect what you select in PAW with what you picked you'd want to push to begin with and at best make the number of files in GIT only smaller, yet still remove the other files if the fundamental disconnect isn't tackled.

    Just to be clear, not saying GIT integration can't be (ab-)used to move objects, but only that that is not source control for which the GIT integration capability in TM1 was designed/intended.

    Cheers,



    ------------------------------
    Hubert Heijkers
    STSM, Program Director TM1 Functional Database Technology and OData Evangelist
    ------------------------------



  • 4.  RE: Git Integration With PAW

    Posted 05/06/26 06:46 AM

    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



    ------------------------------
    Ajit Kumar
    ------------------------------



  • 5.  RE: Git Integration With PAW

    Posted 05/07/26 02:34 PM

    Hi Ajit,

    Expecting 12.6 or later,

    Best regards,



    ------------------------------
    Svetlana Pestsova
    IBM Planning Analytics Product Manager
    ------------------------------



  • 6.  RE: Git Integration With PAW

    Posted 05/07/26 03:34 PM

    Hi Svetlana,

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



    ------------------------------
    Roman Harasymiak
    ------------------------------



  • 7.  RE: Git Integration With PAW

    Posted 05/07/26 03:50 PM

    Hi Roman,

    It's for v12 only. PAW should be able to pick it up quickly, but no version yet.

    Best regards,



    ------------------------------
    Svetlana Pestsova
    IBM Planning Analytics Product Manager
    ------------------------------



  • 8.  RE: Git Integration With PAW

    Posted 11 hours ago

    Hubert's distinction is the one that matters for Ajit's case.

    If the branch is treated as "whatever PAW just pushed," then pushing 2 of 10 TIs should leave 8 files behind. Git already works that way. Replacing the branch contents with the selected objects is snapshot/promote behaviour, not a commit.

    Selective push in 12.6 may shrink the set you send. It does not fix the model if unselected, already-tracked files are still dropped. The test is simple: after a push of two changed processes, do the other eight blobs still have their previous commits on that branch?

    Until the integration commits a delta against the existing tree, this stays a packaged object move that happens to use Git as the transport. Fine for promote. Not source control - and on v11 it will stay that way even after 12.6.



    ------------------------------
    Vitalij Rusakovskij
    ------------------------------



  • 9.  RE: Git Integration With PAW

    Posted 9 hours ago

    Just letting you know selective push in TM1 is still being actively worked on and therefore did not make it into TM1 v12.6. Hopefully 12.7, fingers crossed ;-)



    ------------------------------
    Hubert Heijkers
    STSM, Program Director TM1 Functional Database Technology and OData Evangelist
    ------------------------------



  • 10.  RE: Git Integration With PAW

    Posted 7 hours ago

    Thanks for the update, Hubert.

    Good to know that selective push is still actively being worked on. The distinction between selective object movement and actual Git-based source control is important here.

    I think the interesting question for 12.7 will therefore be whether selective push also preserves the existing Git tree/branch state and creates a delta against it, rather than simply reducing the set of objects being pushed.

    That would be the point where the integration starts behaving more like actual source control rather than object transport via Git.



    ------------------------------
    Vitalij Rusakovskij
    ------------------------------