Re: Best practices for working with GIT

Hi Martijn,

We have done RDI iProjects combined with an SCM for fifteen years now.
First we used Subversion, and later moved to Git.
In our environment each library has its own iProject. The full iProject
(including the .ibmi folder and its content) is stored in the Git repo.
That approach worked well for us, but it is a real challenge to keep track
of what has been pushed to the ibmi libraries. The challenge is not in
using Git, but in the push/pull mechanism of the iProjects, and not
forgetting to push the right sources when you checkout another git branch
with your iProject.

We are in a stage of moving to Code4i, but I'm still looking for a proper
way to convert our iProject sources with sourceorbit and/or bob to a good
IFS structure, without losing fifteen years of change history.
I really look forward to fully use the power of code4i, sourceorbit,
irpgunit, and devops pipelines to test and build.

Long story short: IMO using iProjects brings no extra profit, but adds more
overhead. Look at code4i if you don't want to use a change management
package.

Regards,
-Arco


Op do 18 sep. 2025 10:56 schreef Martijn van Breden <
m.vanbreden@xxxxxxxxxxxxxxxxxxxxxxxxxx>:

Hi all,

We're currently investigating how we can implement git (via eGit) in our
workflow. There are so many possibilities that we're getting a bit lost.
<->
8 What is the preferred way of interaction between i Projects and eGit?

I hope some of you have far more experience than we have and can help us
further on this topic.


Kind regards,

Martijn van Breden

lead software architect