Skip to content

Don't create CI run if pull_request is from same repo #161

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

Closed
3 tasks
emteknetnz opened this issue Mar 19, 2025 · 3 comments
Closed
3 tasks

Don't create CI run if pull_request is from same repo #161

emteknetnz opened this issue Mar 19, 2025 · 3 comments
Assignees

Comments

@emteknetnz
Copy link
Member

emteknetnz commented Mar 19, 2025

In some scenarios a pull-request isn't created from a fork of the repo, instead it done from the same repo

Because there are both pull_request and push triggers on the jobs, two essentially identical CI jobs are run. While this has no real cost of open-source repos, on private repos it wastes github action credits

Acceptance criteria

  • Detect if a pull request originates from a fork or the same repository.
  • Prevent duplicate CI jobs by ignoring the push trigger for internal PRs.
  • This logic is applied to all supported repos (i.e. use shared ci.yml or use module standardiser)

PRs

Module standariders PRs

@GuySartorelli
Copy link
Member

Missing new CMS 6 modules.

@GuySartorelli
Copy link
Member

Also, should target next-patch branch (e.g. 5.3) so PRs there get the same treatment.

@GuySartorelli
Copy link
Member

GuySartorelli commented Apr 7, 2025

All PRs merged

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

No branches or pull requests

2 participants