CoreModernization48 min
Git and GitHub for mainframe developers
Git as a mainframe team uses it every day: VS Code next to ISPF, a clean history, branches and reviewed pull requests, release and hotfix branches with tags, protected branches, and how library stages and EBCDIC code pages map onto Git.
What you will be able to do
- Work on mainframe source in VS Code with the editor, search, terminal and z/OS extensions
- Use Git day to day: status, staging, commits, history, differences and ignored files
- Review changes in pull requests, resolve merge conflicts, and run release and hotfix branches with tags
- Explain branch protection, and map library stages, packages and EBCDIC encodings to Git
Lessons
- VS Code for daily mainframe workMany mainframe teams now edit COBOL, JCL and copybooks in Visual Studio Code next to the ISPF screens they already know.
- Git hands-on: status, staging, commits and historyEvery Git change follows the same loop: change files, look at git status and git diff, stage exactly what belongs to the change with git add, record it with git commit, and read…
- Branches, pull requests, reviews and conflictsEach change gets its own branch. When it is ready you push it and open a pull request, where colleagues review it and automated checks run before it is merged into main.
- Release branches, hotfixes and tagsA release branch holds exactly what production runs, and a tag marks each released version.
- Branch protection and change approvalProtected branches turn a team's change rules into settings the server enforces: changes arrive only through pull requests, with a number of approving reviews and passing status…
- From library stages to Git: source management and code pagesLibrary managers such as Endevor and ChangeMan ZMF move source through stages like development, test, QA and production, with packages and approvals.
Track your progress and earn a certificate.
Free account, 30 quiz questions for this subject.