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.

Sign up for GitHub

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

Jump to bottom

fix(dev-infra): do not run the lock-closed GitHub action on forks #36000

Closed
wants to merge 1 commit into from
Closed

fix(dev-infra): do not run the lock-closed GitHub action on forks #36000

wants to merge 1 commit into from

Commits on Mar 10, 2020

  1. fix(dev-infra): do not run the lock-closed GitHub action on forks 

    Previously, the `lock-closed` GitHub action, which runs daily and locks
closed inactive issues, was run on each fork of the `angular/angular`
repo. While the action is a [no-op on forks][1], it make still fail from
time to time, generating a confusing notification e-mail for the fork
owner.

This commit configures the `lock-closed` action to only run on the main
`angular/angular` repository (using the method suggested [here][2]).

[1]: https://github.com/angular/dev-infra/blob/13b25d383/github-actions/lock-closed/src/main.ts#L117
[2]: https://github.community/t5/GitHub-Actions/Do-not-run-cron-workflows-in-forks/td-p/46756
    @gkalpak
    gkalpak committed Mar 10, 2020
    Configuration menu
    Copy the full SHA
    e4a6e90 View commit details
    Browse the repository at this point in the history