George Kalpakas b99b80c18b fix(dev-infra): do not run the `lock-closed` GitHub action on forks (#36000) ... 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 PR Close #36000		2020-03-11 14:45:47 -04:00
..
ISSUE_TEMPLATE	ci: update issue template for Angular Material to be Angular Components (#32481)	2019-09-04 15:39:44 -07:00
workflows	fix(dev-infra): do not run the `lock-closed` GitHub action on forks (#36000)	2020-03-11 14:45:47 -04:00
ISSUE_TEMPLATE.md	docs: new GitHub Issue templates (#26918)	2018-11-05 09:51:14 -08:00
PULL_REQUEST_TEMPLATE.md	docs: fix formatting of PULL_REQUEST_TEMPLATE.md (#26512)	2018-10-17 13:09:45 -07:00
angular-robot.yml	ci: Migrate from CODEOWNERS to PullApprove for PR review management (#34814)	2020-01-28 09:19:34 -08:00