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

Discord announcement: push only when label "Needs review" is set #7075

Merged
merged 4 commits into from
Aug 20, 2024

Conversation

igorpecovnik
Copy link
Member

@igorpecovnik igorpecovnik commented Aug 13, 2024

Description

As tittle said.

How Has This Been Tested?

Need to be tested.

Checklist:

  • My changes generate no new warnings
  • Any dependent changes have been merged and published in downstream modules

@github-actions github-actions bot added size/small PR with less then 50 lines GitHub Actions GitHub Actions code labels Aug 13, 2024
@igorpecovnik igorpecovnik added 08 Milestone: Third quarter release Needs review Seeking for review and removed Needs review Seeking for review labels Aug 13, 2024
@igorpecovnik igorpecovnik added the Needs review Seeking for review label Aug 13, 2024
@igorpecovnik igorpecovnik force-pushed the on-label branch 2 times, most recently from 35c0b36 to b987371 Compare August 13, 2024 09:24
@igorpecovnik igorpecovnik reopened this Aug 13, 2024
@igorpecovnik igorpecovnik added Needs review Seeking for review and removed Needs review Seeking for review labels Aug 13, 2024
@igorpecovnik igorpecovnik added Needs review Seeking for review and removed Needs review Seeking for review labels Aug 13, 2024
@igorpecovnik igorpecovnik added Needs review Seeking for review and removed Needs review Seeking for review labels Aug 13, 2024
@igorpecovnik igorpecovnik added 08 Milestone: Third quarter release Needs review Seeking for review and removed Needs review Seeking for review 08 Milestone: Third quarter release labels Aug 13, 2024
@EvilOlaf
Copy link
Member

This could trigger the flow to be executed more than once for the same pr. I'd try to avoid that. 1 announce per PR at most. If this is when somebody adds "need review" label its fine too.

@igorpecovnik igorpecovnik added Needs review Seeking for review and removed Needs review Seeking for review labels Aug 13, 2024
@igorpecovnik igorpecovnik added Needs review Seeking for review and removed Needs review Seeking for review labels Aug 13, 2024
@igorpecovnik igorpecovnik added Needs review Seeking for review and removed Needs review Seeking for review labels Aug 13, 2024
@ColorfulRhino ColorfulRhino removed the Needs review Seeking for review label Aug 15, 2024
@ColorfulRhino ColorfulRhino added Needs review Seeking for review and removed Needs review Seeking for review labels Aug 15, 2024
@EvilOlaf
Copy link
Member

I'd say either revert to initial state which was working and let forks handle resulting errors by themselves (which was the reason why we started bothering with permissions and stuff) or remove completely again since this gets ridiculous for a simple push to chat.

@ColorfulRhino
Copy link
Collaborator

@EvilOlaf I had updated this PR a few days ago, it should work as expected now as written in the PR title. I don't quite understand, what's the issue you are talking about in your latest comment?

Copy link
Member

@EvilOlaf EvilOlaf left a comment

Choose a reason for hiding this comment

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

Alright, let's see.

@EvilOlaf
Copy link
Member

what's the issue you are talking about in your latest comment?

At initial commit it worked but forks would run into problems since the job would fail.
At the first change it did not work anymore for anyone but Igor for unknown reason.
At its current state I don't even remember if it actually works.
So yeah, can probably only get better.

@EvilOlaf EvilOlaf merged commit e4d75f2 into main Aug 20, 2024
8 checks passed
@EvilOlaf EvilOlaf deleted the on-label branch August 20, 2024 10:04
@EvilOlaf
Copy link
Member

Doesn't work. secret deployment needs verification. I assume it got lost when it has been switch from repo to org secret.

@ColorfulRhino
Copy link
Collaborator

ColorfulRhino commented Aug 20, 2024

Doesn't work. secret deployment needs verification. I assume it got lost when it has been switch from repo to org secret.

Yeah, I too believe that the remaining issue is an issue with the secret, not with the workflow itself.

Run curl -i -H "Accept: application/json" -H "Content-Type: application/json" -X POST --data \
  curl -i -H "Accept: application/json" -H "Content-Type: application/json" -X POST --data \
  "{\"username\": \"Github\", \"avatar_url\": \"\", \"content\": \"\
  :arrow_heading_up: **Pull request** to [$GITHUB_REPOSITORY](<$GITHUB_SERVER_URL/$GITHUB_REPOSITORY>) by [$GITHUB_ACTOR](<$GITHUB_SERVER_URL/$GITHUB_ACTOR>) - **Please review!** \
  :point_right: [Link](<$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/pull/7112>): *$(git show -s --format=%s)*\"}" 
  shell: /usr/bin/bash -e {0}
curl: no URL specified!

Edit: It may even be the same issue as with the pr-build-artifacts.yml workflow (probably a permission issue). This can be tested if @igorpecovnik adds the "Review needed" label to a PR. If that works, it's likely a permission issue with the secret.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
08 Milestone: Third quarter release GitHub Actions GitHub Actions code Needs review Seeking for review size/small PR with less then 50 lines
Development

Successfully merging this pull request may close these issues.

3 participants