From 52494deb521bd7c54cf178ba1f5585ffdc1cd70c Mon Sep 17 00:00:00 2001 From: Mariatta Wijaya Date: Fri, 13 May 2022 11:48:13 -0700 Subject: [PATCH 1/3] Update deployment info --- CONTRIBUTING.rst | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index 8c97341e..e940c6e3 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -18,6 +18,16 @@ will automatically be deployed to Heroku. This process takes less than 5 minutes If after 10 minutes you did not see the changes reflected, please ping one of the collaborators listed below. +To enable Automatic deployment: + +- On the Heroku dashboard for bedevere, choose the "Deploy" tab. +- Scroll down to the "Automatic deploys" section +- Enter the name of the branch to be deployed (in this case: ``main``) +- Check the "Wait for CI to pass before deploy" button +- Press the "Enable automatic deploys" button. + +Once done, merging a PR against the `main` branch will trigger a new deployment. + .. note:: @@ -36,35 +46,25 @@ Heroku admins can do it too. Details at: https://devcenter.heroku.com/articles/heroku-cli -#. Login to Heroku CLI on the command line and follow instructions - - :: +#. Login to Heroku CLI on the command line and follow instructions:: heroku login -#. If you haven't already, get a clone of the bedevere repo - - :: +#. If you haven't already, get a clone of the bedevere repo:: git clone git@github.com:python/bedevere.git - Or, using `GitHub CLI`_ - - :: + Or, using `GitHub CLI`_:: gh repo clone python/bedevere -#. From the ``bedevere`` directory, add the ``bedevere`` Heroku app as remote branch - - :: +#. From the ``bedevere`` directory, add the ``bedevere`` Heroku app as remote branch:: heroku git:remote -a bedevere -#. From the ``bedevere`` directory, push to Heroku - - :: +#. From the ``bedevere`` directory, push to Heroku:: git push heroku main From e5e8bf4f6075fdab7f9fdcab064a60daf4fb525c Mon Sep 17 00:00:00 2001 From: Mariatta Wijaya Date: Fri, 13 May 2022 11:48:46 -0700 Subject: [PATCH 2/3] Update CONTRIBUTING.rst --- CONTRIBUTING.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index e940c6e3..92af9747 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -26,7 +26,7 @@ To enable Automatic deployment: - Check the "Wait for CI to pass before deploy" button - Press the "Enable automatic deploys" button. -Once done, merging a PR against the `main` branch will trigger a new deployment. +Once done, merging a PR against the ``main`` branch will trigger a new deployment. .. note:: From 24a91b1db83455c3cfe21cbc17f1319985792b57 Mon Sep 17 00:00:00 2001 From: Mariatta Wijaya Date: Fri, 20 May 2022 09:31:00 -0700 Subject: [PATCH 3/3] Update CONTRIBUTING.rst Co-authored-by: Ezio Melotti --- CONTRIBUTING.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index 92af9747..191a5e1c 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -26,7 +26,8 @@ To enable Automatic deployment: - Check the "Wait for CI to pass before deploy" button - Press the "Enable automatic deploys" button. -Once done, merging a PR against the ``main`` branch will trigger a new deployment. +Once done, merging a PR against the ``main`` branch will trigger a new +deployment using a webhook that is already set up in the repo settings. .. note::