Github

As of September of 2025, the Customer Solutions team should use Github for source code management.

To use Github, you need to create a Github account and be added to the Digital Science organization.

Naming Conventions

Repository Prefix: All Customer Solutions team repositories must begin with the cust- prefix.
Repository Type: The prefix should be followed by the repository's type: dashboards, pipelines,infrastructure, tools, analysis (no dashboard), models (ML model).
Example: cust-dashboards-project-name
Labels: Apply topics to your projects to aid organization and browsing. At a minimum, include the "customer" label. Additional labels, such as "dashboards," "infrastructure," or "tools," will further improve discoverability in the absence of a traditional folder structure. All repositories migrated from Gitlab include topics based on the Gitlab folder structure. Topics only need to be applied to new repositories.

Sharing with Customer Teams: Share your repositories with the customer team within GitHub. If the the customer team isn't added, other team members won't be able to view the repository.
Please contact#esd-tech-help if you would like teams created for project specific work.

Replacement for Gitlab CI/CD: GitHub Actions replaces Gitlab CI/CD. The concepts between the tools are similar but the implementation and syntax is much different.
Templates: The Infrastructure and Tools team has migrated several repositories to GitHub Actions; these can serve as templates for new projects.
Support: For assistance with GitHub Actions for new projects, consult the Infrastructure and Tools team via #esd-tech-help.

Our team has also used Gitlab for Docker container registries and Python package management.

Current Solution: Continue to utilize Gitlab for Docker container registries and Python package registries.
Future Solution: A new solution is currently being developed. Documentation will be provided once it's ready.