Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,050
    • Issues 44,050
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,306
    • Merge requests 1,306
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #9931
Closed
Open
Issue created Feb 23, 2019 by James Edwards-Jones@jamedjoContributor

GitHub integration should default to "Static status check names"

What

Make "Static status check names" the default for our CI integration with GitHub.

Why

Users will often want our integration to be compatible with "Required status checks", so they can prevent pull requests being merged before a pipeline is complete. We introduced a setting to make this possible, but users shouldn't have to find it and might struggle to understand why this needs to be turned on to make things work.

Related

  • Mentioned in the description in https://gitlab.com/gitlab-org/gitlab-ee/issues/6696
  • Came up in https://gitlab.com/gitlab-org/gitlab-ee/issues/8129#note_144229628
  • Might explain some of the demand for having this in the API in https://gitlab.com/gitlab-org/gitlab-ee/issues/8477.

github_configuration-screenshot

Edited Oct 14, 2019 by Jason Yavorska
Assignee
Assign to
Time tracking