CI/CD - Advanced Features (major differences)

GitLab (fewer requirements)
Minimum hardware requirements: 4 vCPU and 4 GB RAM support up to 500 users. No specific recommendation for disk size.
GitLab Auto DevOps recognizes the code and automatically sets up the end to end template. Preview App before merge to reduce defects, shorten development time. Multi-project pipelines - Set up GitLab CI/CD across multiple projects, so that a pipeline in one project can trigger a pipeline in another project. Visualize the entire pipeline in one place, including all cross-project interdependencies. Parent-Child pipelines, which can run concurrently and save pipeline run times. Merge trains (Premium) to keep the target branch green. In GitLab, it's possible to place the CI/CD configuration file outside the repository, and thus use the same configuration file for a number of projects.
Supporting up to 3000 users, requires 8 vCPUs, 48 GB RAM, 300 GB attached storage, 200 GB root storage.
Workflow templates for a variety of languages and tooling. When setting up workflows in a repository, GitHub analyzes the code in the repository and recommends workflows based on the language and framework in the repository. However, there is no feature similar to GitLab’s Auto DevOps. There is a third-party Github Action Build Chain. It is a tool for GitHub actions to build multiple projects from different repositories in a single action. In GitHub, there is no parent-child workflow feature, resulting in longer pipeline run times. In GitHub, workflow configuration files must be stored in the .github/workflows directory of the repository. If multiple projects using the same build procedure, there need to be multiple copies of the workflow file.