Skip to content

ci/i18n-notify: only run in upstream repository - #2756

Merged
dumbmoron merged 1 commit into
imputnet:mainfrom
eduqr:fix/i18n-notify-fork-prs
Oct 19, 2026
Merged

dumbmoron merged 1 commit into
imputnet:mainfrom
eduqr:fix/i18n-notify-fork-prs

Conversation

@eduqr

@eduqr eduqr commented Oct 19, 2026

Copy link
Copy Markdown
Contributor

For your pull request to not get closed without review, please confirm that:

  • An issue exists where the maintainers agreed that this should be implemented
    (an approved feature request, or confirmed bug).
  • I tested that my contribution works locally, and does not break anything,
    otherwise I have marked my PR as draft.
  • If my contribution is non-trivial, I did not use AI to write most of it.
  • I understand that I will be permanently banned from interacting with this
    organization if I lied by checking any of these checkboxes.

Tested on (check one or more):

  • Windows
  • macOS
  • Linux

The workflow only skips fork -> upstream prs. In a fork, a pr inside that fork has the same head repo and github repository so the job runs there and mentions all translation owners.

Change:

  • Add github.repository == 'imputnet/helium' so the job only runs in the upstream repo.

Fixes #2752

- add a repository check so the job doesn't run in forks
@greptile-apps

greptile-apps Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

RetriggerView in Greptile

[Low impact] This PR appears safe to merge.

Reviews (1) · Last reviewed commit: "ci/i18n-notify: only run in upstream rep..." · Reviewed by Greptile

@dumbmoron
dumbmoron merged commit 3423b16 into imputnet:main Oct 19, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: ci/i18n-notify still notifying on fork PRs

2 participants