From ff5493f494db7d1a5cc04b3aaa62bfb502c2c609 Mon Sep 17 00:00:00 2001 From: jrfnl Date: Sat, 12 Jun 2021 10:22:00 +0200 Subject: [PATCH] Update all branch references ... from `master` to `stable` for the release branch and from `master` to `develop` for the develop branch. The branch rename from `master` to `stable` and the merging of this PR should be closely coordinated. I'd recommend using the GH interface to do the rename so open PRs and such will be automatically updated: https://docs.github.com/en/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch Fixes 463 --- .github/release-checklist.md | 2 +- .github/workflows/quicktest.yml | 2 +- .github/workflows/test.yml | 2 +- README.md | 16 ++++++++-------- docs/why-requests.md | 4 ++-- 5 files changed, 13 insertions(+), 13 deletions(-) diff --git a/.github/release-checklist.md b/.github/release-checklist.md index a41757a50..d72cc0484 100644 --- a/.github/release-checklist.md +++ b/.github/release-checklist.md @@ -1,4 +1,4 @@ -Template to use for release PRs from `develop` to `master` +Template to use for release PRs from `develop` to `stable` =========================================================== :warning: **DO NOT MERGE (YET)** :warning: diff --git a/.github/workflows/quicktest.yml b/.github/workflows/quicktest.yml index b7caa1958..b0bd62620 100644 --- a/.github/workflows/quicktest.yml +++ b/.github/workflows/quicktest.yml @@ -3,7 +3,7 @@ name: Quicktest on: push: branches-ignore: - - master + - stable # Allow manually triggering the workflow. workflow_dispatch: diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml index 301bd49de..a1b859933 100644 --- a/.github/workflows/test.yml +++ b/.github/workflows/test.yml @@ -3,7 +3,7 @@ name: Test on: push: branches: - - master + - stable pull_request: # Allow manually triggering the workflow. workflow_dispatch: diff --git a/README.md b/README.md index e1c75a423..36e08ebbb 100644 --- a/README.md +++ b/README.md @@ -4,12 +4,12 @@ Requests for PHP [![CS](https://github.com/WordPress/Requests/actions/workflows/cs.yml/badge.svg)](https://github.com/WordPress/Requests/actions/workflows/cs.yml) [![Lint](https://github.com/WordPress/Requests/actions/workflows/lint.yml/badge.svg)](https://github.com/WordPress/Requests/actions/workflows/lint.yml) [![Test](https://github.com/WordPress/Requests/actions/workflows/test.yml/badge.svg)](https://github.com/WordPress/Requests/actions/workflows/test.yml) -[![codecov.io](http://codecov.io/github/WordPress/Requests/coverage.svg?branch=master)](http://codecov.io/github/WordPress/Requests?branch=master) +[![codecov.io](http://codecov.io/github/WordPress/Requests/coverage.svg?branch=stable)](http://codecov.io/github/WordPress/Requests?branch=stable) Requests is a HTTP library written in PHP, for human beings. It is roughly based on the API from the excellent [Requests Python library](http://python-requests.org/). Requests is [ISC -Licensed](https://github.com/WordPress/Requests/blob/master/LICENSE) (similar to +Licensed](https://github.com/WordPress/Requests/blob/stable/LICENSE) (similar to the new BSD license) and has no dependencies, except for PHP 5.6+. Despite PHP's use as a language for the web, its tools for sending HTTP requests @@ -93,13 +93,13 @@ Requests::register_autoloader(); Alternatively, you can fetch a [tarball][] or [zipball][]: ```bash -$ curl -L https://github.com/WordPress/Requests/tarball/master | tar xzv +$ curl -L https://github.com/WordPress/Requests/tarball/stable | tar xzv (or) -$ wget https://github.com/WordPress/Requests/tarball/master -O - | tar xzv +$ wget https://github.com/WordPress/Requests/tarball/stable -O - | tar xzv ``` -[tarball]: https://github.com/WordPress/Requests/tarball/master -[zipball]: https://github.com/WordPress/Requests/zipball/master +[tarball]: https://github.com/WordPress/Requests/tarball/stable +[zipball]: https://github.com/WordPress/Requests/zipball/stable ### Using a Class Loader @@ -126,7 +126,7 @@ Requests is [100% documented with PHPDoc](https://requests.ryanmccue.info/api/). If you find any problems with it, [create a new issue](https://github.com/WordPress/Requests/issues/new)! -[prose-based documentation]: https://github.com/WordPress/Requests/blob/master/docs/README.md +[prose-based documentation]: https://github.com/WordPress/Requests/blob/stable/docs/README.md [request_method]: https://requests.ryanmccue.info/api/class-Requests.html#_request Testing @@ -154,7 +154,7 @@ Contribute 1. Check for open issues or open a new issue for a feature request or a bug 2. Fork [the repository][] on Github to start making your changes to the - `master` branch (or branch off of it) + `develop` branch (or branch off of it) 3. Write a test which shows that the bug was fixed or that the feature works as expected 4. Send a pull request and bug me until I merge it diff --git a/docs/why-requests.md b/docs/why-requests.md index 1e66cc370..6f14910f5 100644 --- a/docs/why-requests.md +++ b/docs/why-requests.md @@ -58,9 +58,9 @@ Why should I use Requests? authentication handlers and cookie support is actually handled internally with hooks. -[codecov]: https://app.codecov.io/gh/WordPress/Requests/branch/master +[codecov]: https://app.codecov.io/gh/WordPress/Requests/branch/stable [hooking system]: hooks.md -[requests_ssl]: https://github.com/WordPress/Requests/blob/master/library/Requests/SSL.php +[requests_ssl]: https://github.com/WordPress/Requests/blob/stable/library/Requests/SSL.php [ghactions]: https://github.com/WordPress/Requests/actions [wpssl]: http://core.trac.wordpress.org/ticket/25007