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

chore: robustify PR release workflow #3051

Merged
merged 1 commit into from
Dec 12, 2023
Merged

Conversation

nomeata
Copy link
Collaborator

@nomeata nomeata commented Dec 12, 2023

the workflow is triggered not only by pull-request-CI-runs but also by
others. These should be skipped.

Also, no need to query the Github API to get the pull request number and
head sha, they are part of the payload, it seems.

@nomeata nomeata requested review from Kha and kim-em as code owners December 12, 2023 10:01
@nomeata nomeata force-pushed the joachim/fix-pr-release branch from 83f0760 to e776021 Compare December 12, 2023 10:02
the workflow is triggered not only by pull-request-CI-runs but also by
others. These should be skipped.

Also, no need to query the Github API to get the pull request number and
head sha, they are part of the payload, it seems.
@nomeata nomeata force-pushed the joachim/fix-pr-release branch from e776021 to e4b28e8 Compare December 12, 2023 10:02
@github-actions github-actions bot added the toolchain-available A toolchain is available for this PR, at leanprover/lean4-pr-releases:pr-release-NNNN label Dec 12, 2023
@leanprover-community-mathlib4-bot
Copy link
Collaborator

  • ❗ Mathlib CI will not be attempted unless you rebase your PR onto the 'nightly' branch. (2023-12-12 10:19:55)

@Kha
Copy link
Member

Kha commented Dec 12, 2023

If they are part of the payload, can't we directly access them in ${{ }}?

@nomeata
Copy link
Collaborator Author

nomeata commented Dec 12, 2023

Yes, but it makes the if condition and the value even longer, so I left it like this. I can change it if you dislike it; not feeling strongly about it.

@Kha
Copy link
Member

Kha commented Dec 12, 2023

Ok, fine with me

@nomeata nomeata added this pull request to the merge queue Dec 12, 2023
})
core.setOutput('pullRequestNumber', reply.data.pull_requests[0].number)
core.setOutput('sourceHeadSha', reply.data.pull_requests[0].head.sha)
// console.log(`context.payload: ${JSON.stringify(context.payload, null, 2)}`)
Copy link
Member

Choose a reason for hiding this comment

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

Will the comment stay in there? :)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes, it's useful for debugging to not have to look it up everytime :-)

(unless you mind)

Merged via the queue into master with commit 6a629f7 Dec 12, 2023
7 checks passed
@nomeata nomeata deleted the joachim/fix-pr-release branch December 12, 2023 21:48
@nomeata
Copy link
Collaborator Author

nomeata commented Dec 12, 2023

@Kha
Copy link
Member

Kha commented Dec 13, 2023

classic undefined behavior

@nomeata
Copy link
Collaborator Author

nomeata commented Dec 13, 2023

Should have left the debugging output on :-)

But that was this odd very old PR that got activated, maybe that played a role. I'll keep an eye open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
toolchain-available A toolchain is available for this PR, at leanprover/lean4-pr-releases:pr-release-NNNN
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants