When you migrate repositories to or from GitHub products, your origin and destination repositories may be “locked” for migration. While a repository is locked, you cannot make any changes to the repository, such as pushing commits, creating issues, or commenting on pull requests., A lock file already exists in the repository, which blocks this operation from completing. Upon searching the internet, the only solution I've found is to delete index.lock file inside .git folder manually., In this post, I’ll introduce a GitHub Action for implementing a lock mechanism. https://github.com/suzuki-shunsuke/lock-action. Manage branches via GitHub API without git command. You don't have to checkout repositories by actions/checkout. This action requires two inputs: key and mode., Repositories can be locked to prevent changes, often for migrations. When you migrate repositories to or from {% data variables.product.prodname_dotcom %} products, your origin and destination repositories may be “locked” for migration., GitHub provides a powerful tool called “Locking.” In this post, we’ll explore how to use GitHub’s locking feature to avoid conflicts and maintain order in your collaborative projects., Optional reason for locking conversation (off_topic, resolved, spam, too_heated)..