@@ -18,6 +18,17 @@ will automatically be deployed to Heroku. This process takes less than 5 minutes
18
18
If after 10 minutes you did not see the changes reflected, please ping one
19
19
of the collaborators listed below.
20
20
21
+ To enable Automatic deployment:
22
+
23
+ - On the Heroku dashboard for bedevere, choose the "Deploy" tab.
24
+ - Scroll down to the "Automatic deploys" section
25
+ - Enter the name of the branch to be deployed (in this case: ``main ``)
26
+ - Check the "Wait for CI to pass before deploy" button
27
+ - Press the "Enable automatic deploys" button.
28
+
29
+ Once done, merging a PR against the ``main `` branch will trigger a new
30
+ deployment using a webhook that is already set up in the repo settings.
31
+
21
32
22
33
.. note ::
23
34
@@ -36,35 +47,25 @@ Heroku admins can do it too.
36
47
37
48
Details at: https://devcenter.heroku.com/articles/heroku-cli
38
49
39
- #. Login to Heroku CLI on the command line and follow instructions
40
-
41
- ::
50
+ #. Login to Heroku CLI on the command line and follow instructions::
42
51
43
52
heroku login
44
53
45
54
46
- #. If you haven't already, get a clone of the bedevere repo
47
-
48
- ::
55
+ #. If you haven't already, get a clone of the bedevere repo::
49
56
50
57
git clone [email protected] :python/bedevere.git
51
58
52
- Or, using `GitHub CLI `_
53
-
54
- ::
59
+ Or, using `GitHub CLI`_::
55
60
56
61
gh repo clone python/bedevere
57
62
58
- #. From the ``bedevere `` directory, add the ``bedevere `` Heroku app as remote branch
59
-
60
- ::
63
+ #. From the ``bedevere `` directory, add the ``bedevere `` Heroku app as remote branch::
61
64
62
65
heroku git:remote -a bedevere
63
66
64
67
65
- #. From the ``bedevere `` directory, push to Heroku
66
-
67
- ::
68
+ #. From the ``bedevere `` directory, push to Heroku::
68
69
69
70
git push heroku main
70
71
0 commit comments