Skip to content

Commit

Permalink
Create repo-lockdown GitHub action
Browse files Browse the repository at this point in the history 
This change adds a new GitHub action which automatically closes all GitHub issues or pull requests and redirects users to Unreal Engine support.
  • Loading branch information
@bcbee
bcbee authored Jun 5, 2022
1 parent d9077bb commit 55e5226
Showing 1 changed file with 22 additions and 0 deletions.
22 changes: 22 additions & 0 deletions .github/workflows/lockdown.yml
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
name: 'Repo Lockdown'

This comment has been minimized.

Sign in to view

Copy link
@zolex

zolex Jun 6, 2022 •
edited
Loading

Member

You can simply disable issues in the repo settings ^^

This comment has been minimized.

Sign in to view

Copy link
@bcbee

bcbee Jun 6, 2022

Author Contributor

This is not entirely possible, see: https://stackoverflow.com/questions/27957454/how-to-disable-pull-requests-in-github. While there are ways to prevent people from merging PRs (branch protection) there isn't a good way to prevent them from being created in the first place, which is the issue here. Pull Requests are not a feature that can be disabled entirely in the settings like issues/wiki/etc.

This comment has been minimized.

Sign in to view

Copy link
@nutterthanos

nutterthanos Jun 7, 2022

or is it possible to move the signup to a placeholder account which after sign up gives you access to the EpicGames Repos/Org

on:
issues:
types: opened
pull_request_target:
types: opened
schedule:
- cron: '0 * * * *'

permissions:
issues: write
pull-requests: write

jobs:
action:
runs-on: ubuntu-latest
steps:
- uses: dessant/repo-lockdown@v2
with:
issue-comment: 'Epic Games does not accept issues on this repository. Please visit https://www.unrealengine.com/support for support.'
pr-comment: 'Epic Games does not accept pull requests on this repository. Please visit https://www.unrealengine.com/support for support.'

0 comments on commit 55e5226

Please sign in to comment.