I think the build failed because of the trigger setup on the .drone.yml file which still triggers the deployment process but the ssh key secret is locked out of pull requests. I think the the following patch might fix that:
LGTM!
I think the build failed because of the trigger setup on the [.drone.yml](https://git.autonomic.zone/autonomic-cooperative/autonomic.zone/src/branch/master/.drone.yml) file which still triggers the deployment process but the ssh key secret is locked out of pull requests. I think the the following patch might fix that:
```diff
diff --git a/.drone.yml b/.drone.yml
index 2b6e593..29fe7cd 100644
--- a/.drone.yml
+++ b/.drone.yml
@@ -11,3 +11,6 @@ steps:
trigger:
branch:
- master
+ event:
+ exclude:
+ - pull_request
```
We just need something to ignore pull requests and only deploy on master merges. I was looking at https://docs.drone.io/pipeline/triggers/ for that.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Closes #16
LGTM!
I think the build failed because of the trigger setup on the .drone.yml file which still triggers the deployment process but the ssh key secret is locked out of pull requests. I think the the following patch might fix that:
We just need something to ignore pull requests and only deploy on master merges. I was looking at https://docs.drone.io/pipeline/triggers/ for that.
OK, let's merge this.