-
Notifications
You must be signed in to change notification settings - Fork 1.2k
🏃 use new github action syntax #735
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
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: alexeldeib The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
41fa4df
to
01369c4
Compare
c857ede
to
f4d0281
Compare
I think github is unhappy because I am trying to merge into the main workflow: https://i.8713187.xyzmunity/t5/GitHub-Actions/GitHub-action-Resource-not-accessible-by-integration/td-p/19707 However I have an up to date fork where this action works fine: https://github.com/alexeldeib/controller-runtime/commit/f4d028132839d6df1e3d815d0f016ca4a4c17724/checks?check_suite_id=365691723 |
f4d0281
to
dbd8f79
Compare
dbd8f79
to
12317e1
Compare
I'm not sure that's the issue, actually. But since actions show up as a check anyway, maybe it's sufficient to leave it like this without the CURL to set status? I guess the text won't pretty print for the unicode emoji, but the check will work at least shrugs |
Nice, let's get the check back in place, then I'll play around with the pretty-printing. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can also move those dockerfile labels into a check metadata file: https://help.github.com/en/actions/automating-your-workflow-with-github-actions/creating-a-docker-container-action#create-an-action-metadata-file
.github/workflows/main.yaml
Outdated
@@ -0,0 +1,12 @@ | |||
on: pull_request |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This changed since I originally wrote this, but I think we want to explicitly list types so we get edit
as a type here as well: https://help.github.com/en/actions/automating-your-workflow-with-github-actions/events-that-trigger-workflows#pull-request-event-pull_request
@@ -25,5 +25,10 @@ base_link=$(jq -r '.pull_request.url' < ${GITHUB_EVENT_PATH}) | |||
head_commit=$(curl -H "Authorization: Bearer ${GITHUB_TOKEN}" -H 'Accept: application/vnd.github.antiope-preview+json' -q ${base_link} | jq -r '.head.sha') | |||
echo "head commit is ${head_commit}" | |||
|
|||
curl https://api.github.com/repos/${GITHUB_REPOSITORY}/check-runs -XPOST -H "Authorization: Bearer ${GITHUB_TOKEN}" -H 'Accept: application/vnd.github.antiope-preview+json' -H 'Content-Type: application/json' -q --data-raw '{"name": "Verify Emoji", "head_sha": "'${head_commit}'", "conclusion": "'${conclusion}'", "status": "completed", "completed_at": "'$(date -Iseconds)'", "output": {"title": "Verify Emoji", "summary": "'"${summary}"'"}}' | |||
echo ${summary} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe it's just me, but I'm not actually seeing the output of this in the result. Let me try manually re-running.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah, it just shows up way at the bottom. Need to scroll.
26a5dfa
to
8b6450d
Compare
I updated the triggers, but I feel like something weird is happening with the display of the check still..seems like it's showing twice? |
@alexeldeib: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
:bugfix: avoid duplicate import/add-to-scheme code snippets
This is stale and doesn't produce the desired behavior anyway, going to close. I think we probably just want to run this script in prow and exit 1 if failed, or else fail the action directly rather than post back to the checks API. |
I played around a bit and got it almost working, but got side-tracked :-/ The problem with prow is that it won't recheck on edits to the title, IIRC -- you'd have to manually run "retest". We'd need a plugin or something. |
fixes #610
get those sweet, sweet emoji verified