-
Notifications
You must be signed in to change notification settings - Fork 92
ci: Restrict deployments of environments to PR merges #1960
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
* The actions/upload-pages-artifacts action deploys an environment so to avoid unnecessary deployments only have it run on pushes to master which occur on PR merges.
|
Hm. @kratsg this isn't having the intended effect with deployment history. |
Codecov Report
@@ Coverage Diff @@
## master #1960 +/- ##
=======================================
Coverage 98.24% 98.24%
=======================================
Files 68 68
Lines 4380 4380
Branches 728 728
=======================================
Hits 4303 4303
Misses 45 45
Partials 32 32
Flags with carried forward coverage won't be shown. Click here to find out more. Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
|
Is this still a draft? |
Yes, as this isn't having the intended effect. c.f. #1960 (comment) |
It should be fixed now. I moved the environment + permissions to a deploy job and that job only runs on master. Pages artifacts still uploads, but now the environment isn't being created or deployed to. |

Description
Split the docs workflow into a build and deploy jobs, where the deploy job requires the build job to succeed. This avoids unnecessary deployments by only having the github-pages environment exist in the deploy job.
Checklist Before Requesting Reviewer
Before Merging
For the PR Assignees: