Skip to content

Conversation

@jeresig
Copy link
Member

@jeresig jeresig commented May 7, 2025

Summary:

We don't want Gerald to run when making a PR against main/master - as we're typically using a merge queue in this scenario and don't want the double-review.

Issue: FEI-6249

Test plan:

@jeresig jeresig self-assigned this May 7, 2025
@jeresig jeresig requested a review from lillialexis May 7, 2025 14:20
@khan-actions-bot khan-actions-bot requested a review from a team May 7, 2025 14:20
@khan-actions-bot
Copy link
Contributor

Gerald

Required Reviewers
  • @Khan/github-actions for changes to dist/index.js, src/runOnPullRequest.js

Don't want to be involved in this pull request? Comment #removeme and we won't notify you of further changes.

// NOTE: We don't want to run Gerald when we're merging a PR into
// master or main, as this is likely a deploy branch that only contains
// landed PRs that have already been reviewed.
const IGNORED_PR_REFS = ['master', 'main'];
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think we want to do this here, since many repos do land straight to main / master. Instead, we can control this repo-by-repo with their own yaml files that call Gerald.

Copy link
Contributor

@lillialexis lillialexis left a comment

Choose a reason for hiding this comment

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

Isn't this better to do in each repo's yaml file? I really do want Gerald to add the github-actions team to all of my OLC changes, for example, many/most of which target main.

@jeresig
Copy link
Member Author

jeresig commented May 7, 2025

Ah, so updated the gerald-pr.yml file in frontend/webapp so that if we're landing on to main/master we just bail - I can do that!

@jeresig jeresig closed this May 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants