From 99680be1dfe6bea2e75204cf14daa673a06aba38 Mon Sep 17 00:00:00 2001 From: Shivam Mathur Date: Sat, 23 Sep 2023 03:29:31 +0530 Subject: [PATCH] Rename branch in README --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index aa6e3531..06937d45 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,7 @@

GitHub Actions status Codecov Code Coverage - LICENSE + LICENSE PHP Versions Supported

@@ -942,7 +942,7 @@ Examples of using `setup-php` with various PHP frameworks and packages. - Semantic release versions can also be used. It is recommended to [use dependabot](https://docs.github.com/en/github/administering-a-repository/keeping-your-actions-up-to-date-with-github-dependabot "Setup Dependabot with GitHub Actions") with semantic versioning to keep the actions in your workflows up to date. - Commit SHA can also be used, but are not recommended. They have to be updated with every release manually, without which you will not get any bug fixes, security patches or new features. - For debugging any issues `verbose` tag can be used temporarily. It outputs all the logs and is also synced with the latest releases. -- It is highly discouraged to use the `master` branch as version, it might break your workflow after major releases as they have breaking changes. +- It is highly discouraged to use the `main` branch as version, it might break your workflow after major releases as they have breaking changes. - If you are using the `v1` tag or a `1.x.y` version, you should [switch to v2](https://github.com/shivammathur/setup-php/wiki/Switch-to-v2 "Guide for switching from setup-php v1 to v2") as `v1` only gets critical bug fixes. Maintenance support for `v1` will be dropped with the last `PHP 8.0` release. ## :scroll: License