Interesting document. Thanks for sharing the content and considering iForGit.
I like your concept of a check-out/check-in command to move source members to a developer's library. That's one way of having your own custom development processes but also manage source in a git repository.
As an aside - I'm currently working on an addon component that's called BLDONI (Build on i) - which has some of the componentry that you would need to create a request and check out code for development to a dev library and check it back in when development is done. All compatible with iForGit commands.
Anyway thanks for sharing your writeup.
Regards,
Richard Schoen
Web:
http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
------------------------------
message: 2
date: Tue, 31 Jan 2023 09:34:42 -0600
from: Steve M via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>
subject: RE: Understanding GIT from an IBM i (RPGLE, CLLE, DDS)
prospective
Okay, here is a link to my document:
https://www.dropbox.com/scl/fi/k2gikqdixxe3ceb76kmoq/GitLab-and-RPG-POC.docx
?dl=0&rlkey=y8x61q2dbd8jvglt5xbzzfva7
It was a few years ago, but I think the processes and concepts are still solid. Yes, you will see both RDi and SEU support in the document (I was working with a couple of developers who, under no circumstances would use RDi, so I had to find solutions that worked in both IDE worlds).
Steve
midrange.com
