Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • A Axi Pulp
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • 小 白蛋
  • Axi Pulp
  • Repository
Switch branch/tag
  • axi-pulp
  • .github
  • workflows
  • gitlab-ci.yml
Find file BlameHistoryPermalink
  • Andreas Kurth's avatar
    workflows/gitlab-ci: Fix SHA for pull request · 049ca4e3
    Andreas Kurth authored Jan 14, 2021
    For `pull_request` events, `GITHUB_SHA` is not the SHA of the HEAD
    commit of the pull request branch but of the merge commit created by
    GitHub [1].  Apparently, this is even the case when there is no merge
    commit because the action checks out the HEAD commit (bug?).
    
    [1]: https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows#pull_request
    049ca4e3

免费DevSecOps平台,让您的项目体验完整的DevSecOps流程,让项目更安全