Skip to content

PR gate fails every release PR not opened from dev #195

Description

@saqibmanan

What: the PR gate passes the PR head SHA as deployed_sha, and api-smoke asserts dev's /health/ git_sha matches it. A release PR from any branch other than dev always fails that check.

Evidence: #191 (from a release branch built to resolve conflicts): 40 passed, 1 failed — Deployed git_sha 'eaf5a1c…' does not match expected '3bab067…'. #194, opened straight from dev, passed.

Fix: not fixed — compare against dev's head instead of the PR head. Applies to DataSpaceBackend and DataSpaceFrontend pr-gate.yml.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions