Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(release): Add statusProvider context check for craft #8685

Merged
merged 1 commit into from
Aug 1, 2023

Conversation

mydea
Copy link
Member

@mydea mydea commented Jul 31, 2023

To ensure we wait for the correct check to pass before continuing with publishing.
I think it is correct to use the "human readable" name of the check (??), at least the example looks similar. This is an example for what we are waiting for: https://github.com/getsentry/sentry-javascript/actions/runs/5715683859/job/15486522728

If I understand this correctly, this was completely broken and just looked for any (??) successful check..?!

See getsentry/craft#482

To ensure we wait for the correct check to pass before continuing with publishing.
@mydea mydea added the Dev: CI label Jul 31, 2023
@mydea mydea requested review from asottile-sentry and a team July 31, 2023 16:15
@mydea mydea self-assigned this Jul 31, 2023
Copy link
Member

@AbhiPrasad AbhiPrasad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good catch!

@mydea mydea merged commit e1e0a3c into develop Aug 1, 2023
78 checks passed
@mydea mydea deleted the fn/craft-check branch August 1, 2023 07:37
Lms24 added a commit that referenced this pull request Aug 3, 2023
Lms24 added a commit that referenced this pull request Aug 3, 2023
…8685) (#8729)

Seems like the `context` passed isn't found which is blocking our
release. Reverting for now until we know how to configure the status
provider correctly (getsentry/craft#482).

#uncraft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants