> Markdown version of [/jobs/ext/4805785-configuration-source-code-repository-lead](https://www.wearedevelopers.com/jobs/ext/4805785-configuration-source-code-repository-lead). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Configuration/Source Code Repository Lead - **Company:** TISTA Science and Technology Corporation - **Location:** United States (Remote available) - **Experience:** Expert - **Salary:** $55,546 - $120,875 - **Contract:** Permanent contract - **Skills:** Agile Methodology, JIRA, Audit Trail, Automation of Tests, Unit Testing, Bash Shell, Health Informatics, Configuration Management, Static Program Analysis, Information Systems, Data Dictionary, DevOps, Github, Intrusion Detection Systems, Python (Programming Language), M Programming Language, Open Source Technology, Windows PowerShell, Sharepoint Document Library, Security Assertion Markup Language (SAML), Software Configuration Management, Software Engineering, Management of Software Versions, Scripting, Git, Information Technology, Github Enterprise, Intersystems, Software Version Control, Jenkins - **Published:** November 20, 2026 - **Apply:** https://diversityjobs.com/career/18982586/Configuration-Source-Code-Repository-Lead ## About the Role * Five or more years of experience in software configuration management, release engineering, or DevOps, with at least two years of hands-on experience with Git and GitHub. * At least two years of experience working with MUMPS (M) code and InterSystems Cache or IRIS, including routines, globals, and namespaces. Working knowledge of VistA architecture. * Demonstrated experience defining branching and merging strategies and enforcing them across multi-developer teams. * Experience building CI/CD pipelines using GitHub Actions, Jenkins, or equivalent. * Proficiency with scripting (Bash, PowerShell, or Python) for exporting, importing, and automating code movement. * Knowledge of configuration management principles, including baselines, change control, and audits. * Strong written and verbal communication skills., * Eight or more years of experience in configuration management for large enterprise or government health applications. * Prior experience on VistA sustainment or modernization contracts, including familiarity with the VA Software Document Library, patch release processes, and VistA Evolution or similar programs. * Experience building or using tooling to bridge M and Git (for example, routine export and import utilities, the InterSystems Git integration or source control hooks, or open-source VistA tools). * Experience with M-Unit and automated testing of VistA code, and with code standards tools such as XINDEX. * Experience with the InterSystems ObjectScript VS Code extension and Cache Studio source control hooks. * Experience with GitHub Enterprise administration, SSO/SAML, and audit logging. * Experience with Agile and SAFe in a federal contracting environment. Education: * A bachelor's degree in computer science, information technology, software engineering, information systems, health informatics, or a related field. Per typical contract language, additional years of relevant experience (commonly four to five years) may substitute for a degree, subject to the labor category definition in the contract. Clearance: * Tier 2 / Moderate Risk Background Investigation (VA Handbook 0710); ability to obtain VA PIV credential. ## Description * Design the GitHub organization and repository structure for a large MUMPS code base, including package-based directory layouts (for example, one directory per VistA package or namespace) and a decision on monorepo versus multi-repo. * Establish the repository as the source of truth by exporting routines (.m or .int files), data dictionaries, and other artifacts, and by reconciling differences between development, test, and production accounts. * Configure teams, roles, and least-privilege access integrated with VA identity services, and handle large files and binary artifacts appropriately. Branching, Merging, and Check-In/Check-Out for M Code * Define, document, and enforce a branching strategy suited to VistA patch cadence (for example, trunk-based with short-lived feature branches, plus release and hotfix branches tied to patch streams). * Establish conventions for routine naming, namespace ownership, line-level formatting, and commit messages that reference patch or work item IDs. * Configure branch protection, required reviews, CODEOWNERS by package, and status checks. * Resolve merge conflicts specific to M code, such as concurrent edits to shared routines, and coach developers who are new to Git on pull request workflows. * Provide guidance on keeping Cache namespaces and Git branches synchronized, including import and export procedures for developers working in Studio, VS Code (with the InterSystems ObjectScript extension), or terminal sessions. Workflow Streamlining and Automation * Build CI/CD pipelines using GitHub Actions (self-hosted runners as needed inside the VA boundary) or comparable tools to import code into disposable Cache or IRIS test instances, compile routines, and run automated tests. * Integrate M-aware quality gates, such as the M-Unit testing framework, static analysis and standards checking (for example, XINDEX-style checks or open-source M linters), and routine size and structure checks. * Automate KIDS build and patch assembly, packaging, and installation into target environments where permitted. * Use containerized Cache or IRIS instances for repeatable build and test environments, where approved. * Link commits to Jira or other work items for end-to-end traceability, and standardize issue, pull request, and workflow templates. Configuration Management and Baseline Control * Maintain configuration baselines for routines, globals that carry configuration (such as parameters and file definitions), scripts, and environment settings across dev, test, preproduction, and production. * Manage versioning, tagging, and release candidates consistent with VistA patch version and sequence numbering. Support, Training, and Transition * Serve as the escalation point for repository, build, and release issues. * Collaborate with VistA developers, testers, security staff, product owners, and the Cache/IRIS database administrators.