Developers | University IT

Services and APIs

The RESTful web services provided by Middleware and Integration Services (MaIS) are used to retrieve and modify data from the Registry.

Learn more »

Explore GitLab

Discover projects, groups and snippets. Share your projects with others.

Learn more »

Apple Developer Program

Create applications for Apple hardware platforms with free Apple resources.

Learn more »

Google Play Console

Create applications for Google hardware platforms with free Google resources.

Learn more »

Cardinal Cloud GitHub

Store, manage, and track changes to your code while collaborating with others.

Learn more »

Compare GitLab vs GitHub

Choosing between GitLab and GitHub depends on your specific needs, preferences, and the features each platform offers. Stanford recommends using GitLab for most projects. However, if your project involves contributions from a large number of members, including external collaborators, or requires Microsoft-based plugins like Co-pilot or specific integrations that are only available in GitHub, then GitHub would be the better choice.

When to Use GitLab

Integrated DevOps and CI/CD Pipelines: Use GitLab if you need a comprehensive DevOps platform with integrated Continuous Integration/Continuous Deployment (CI/CD) pipelines. GitLab's built-in CI/CD features are robust, allowing you to manage your entire DevOps lifecycle within a single application, from code commits to deployment.
Complete Application Lifecycle Management: Consider GitLab if you want a platform that supports the entire application lifecycle, from planning and issue tracking to deployment and monitoring. GitLab’s integrated approach can reduce the need for multiple tools and streamline your development process.

When to Use GitHub

Wider Community and Collaboration: Choose GitHub if you value access to a large, active developer community. GitHub is the most popular platform for open-source projects, making it easier to collaborate, contribute, and gain visibility within the developer community.
Familiarity and Popularity: Use GitHub if your team is already familiar with the platform or if GitHub is a standard in your industry or organization. GitHub’s interface and workflow are intuitive and widely adopted, making it easier to onboard new team members.
Integration with GitHub Actions: Opt for GitHub if you want to leverage GitHub Actions for CI/CD workflows. GitHub Actions is tightly integrated with the GitHub platform and provides a powerful and flexible way to automate your development workflows.
Integration with Microsoft tools: GitHub is owned by Microsoft, so it integrates well with Microsoft tools like Azure DevOps, Visual Studio, and Teams.