Merritt Krakowitzer

Also would like to know how to do this.

Crossposting this for completeness, I don't believe this is an API constraint, I tested this now and the API supports added branches that do not exist. ``` mutation MyMutation {...

I don't believe this is an API issue, I tested this now and the API supports wildcards ``` mutation MyMutation { __typename createBranchProtectionRule(input: {repositoryId: "XXXXXXXXXXXXXXXXXX", pattern: "foobar*", restrictsPushes: false}) {...

@trent-j I was wondering if you had a chance to work on this? Its the only thing stopping us from using this action.

I had this issue with puppet 4 on centos 7.1, I installed the gem as follows: ``` /opt/puppetlabs/opt/puppetlabs/puppet/bin/gem install hiera-eyaml ``` Using the below worked for me: ``` /opt/puppetlabs/bin/puppetserver gem...

I kept support for deploy to remain backwards compatible as it was the original module used. I think lets drop support for both deploy and staging in favour of archive,...

this would be a nice feature.

+1

Any plans to implement this feature?

We have this same issue at the moment. Actions triggered by dependabot would fail as it did not have access to secrets, and then someone from the team could retrigger...