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

Remove 'pull_request_review' event from the community contributions spreadsheet action #12950

Merged
merged 1 commit into from
Dec 16, 2024

Conversation

MisRob
Copy link
Contributor

@MisRob MisRob commented Dec 16, 2024

Summary

  • Remove pull_request_review event. When triggered by this event, secrets are not available. This fixes the action failures when a pull request is reviewed, such as here.
  • Remove unnecessary nuanced event settings. Generally the spreadsheet date should get updated on all associated events.

References

https://learningequality.slack.com/archives/CB37UM23A/p1733946399034929

Reviewer guidance

I tested here learningequality/test-actions#60

- Remove `pull-request-review` event. When triggered
  by this event, secrets are not available. This fixes
  the action failure when pull request reviewed.
- Remove unnecessary nuanced event settings. Generally
  the spreadhseet date should get updated on all associated
  events.
@MisRob
Copy link
Contributor Author

MisRob commented Dec 16, 2024

cc @GarvitSinghal47 just if it'd be interesting for learning, we figured out we cannot keep pull_request_review event since it can't access secrets, causing the script fail on missing secrets when triggered by this particular event. This is most likely related to security, even though none of us seem to understand details :) This helps to fix it though.

@rtibbles rtibbles merged commit 9501abb into learningequality:develop Dec 16, 2024
39 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DEV: dev-ops Continuous integration & deployment TODO: needs review Waiting for review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants