dessant / repo-lockdown Goto Github PK

I have included repo-lockdown in my project. My goal is to automatically close all the PR with a message. I tested this exact same file in a private repo to check that it was working as expected and it worked. Now, in a real repository, when I go to Actions in github, it shows:

Run dessant/repo-lockdown@v2
  with:
    github-token: ***
    skip-closed-issue-comment: false
    close-issue: false
    lock-issue: true
    pr-comment: cpufetch does not accept pull requests, see [the contributing guidelines](https://github.com/Dr-Noob/cpufetch/blob/master/CONTRIBUTING.md) for details
    skip-closed-pr-comment: false
    close-pr: true
    lock-pr: false
    process-only: prs
Error: HttpError: Resource not accessible by integration

What is happening?

Hi!

Repo Lockdown has been rewritten for GitHub Actions, offering new features and better control over your automation presets. The legacy GitHub App has been deprecated, and the public instance of the app has been shut down. You're receiving this message because the deprecated app is still installed for your user account or organization.

You can follow the user guide and examples to install the new action for your repositories:

https://github.com/dessant/repo-lockdown

If you need any help with configuring the action, please open an issue or message me at [email protected].

The continued development of Repo Lockdown is made possible thanks to the support of awesome backers. If you'd like to join them, please check out https://github.com/sponsors/dessant

Please ignore the new permission request for the app, it was only used to notify project maintainers directly, without opening thousands of issues.

Thanks,
Armin Sebastian

I wanted to lock PRs in master branch of a repo, but want to allow on other branches.
Will this app help?

Hi

The PostgreSQL project has been using the legacy app to close PRs to all the mirror repos we keep on Github (https://github.com/postgres). I noticed today that the we've had a couple of PRs that haven't been closed, and realised after digging in that you've moved the project to use Github Actions, and deprecated the old Probot app.

For various reasons it's not feasible for us to add a .github directory to the upstream source trees. Are there any plans to support org-wide configuration as we used to use?

Judging by prism-break/prism-break#2034 and some other issues, it seems that repo-lockdown GitHub app has stopped working somewhere around 4 days ago.

action
Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: dessant/repo-lockdown

action
The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Amazing app! I have only one comment. I know there is skipCreatedBefore to set what to process, but I would prefer that all issues and pull requests are closed/locked, but only on those which were initially open a comment is left. Would that be possible?

I would like to use your Repo Lockdown app on a GitHub Enterprise instance. How can I go about setting that up?

It'd be nice to have an exclusion list that can be by username. For example: Only members of the GitHub organization can be allowed to create new issues. This can be part of an exclusion list of usernames. Anyone else not in this list will be subject to the repo-lockdown action.