# Using templates with protected repositories does not work correctly

**URL:** https://drone.discourse.group/t/using-templates-with-protected-repositories-does-not-work-correctly/11743
**Category:** Drone Bugs
**Created:** [March 1, 2022, 8:44pm UTC](https://drone.discourse.group/t/using-templates-with-protected-repositories-does-not-work-correctly/11743 "2022-03-01T20:44:41Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![djmaze](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/djmaze/32/3788_2.png) [@djmaze](https://drone.discourse.group/u/djmaze)
#### Post date: [March 1, 2022, 8:44pm UTC](https://drone.discourse.group/t/using-templates-with-protected-repositories-does-not-work-correctly/11743/1 "2022-03-01T20:44:41Z")

</div>

I added a template to my organization and ported a project’s .drone.yml to use the template instead. As this is a protected repository, I signed the config afterwards using the drone cli, so in this case it looks like this:

```nohighlight
---
kind: template
load: docker-buildx.yaml
data:
  image: my/repository
---
kind: signature
hmac: REDACTED

...

```

Now although the repository is now protected _and_ signed, I still have to manually approve every build. I think there is something wrong here.

---

<div class="post-metadata">

### Author: ![Nico1](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/nico1/32/7665_2.png) [@Nico1](https://drone.discourse.group/u/Nico1)
#### Post date: [May 31, 2022, 9:22am UTC](https://drone.discourse.group/t/using-templates-with-protected-repositories-does-not-work-correctly/11743/2 "2022-05-31T09:22:56Z")

</div>

Same here. Any solution to this?

---

<div class="post-metadata">

### Author: ![Bluebang](https://yyz1.discourse-cdn.com/flex003/user_avatar/drone.discourse.group/bluebang/32/8647_2.png) [@Bluebang](https://drone.discourse.group/u/Bluebang)
#### Post date: [March 1, 2023, 1:27pm UTC](https://drone.discourse.group/t/using-templates-with-protected-repositories-does-not-work-correctly/11743/3 "2023-03-01T13:27:54Z")

</div>

Same here. Any solution to this? 🥲  
@Nico1 @djmaze
