John Martel
John Martel
Sorry for the noisy reference, I was trying to make this work, but was not actually able to, even after trying all possible combinations. I ended up with the following,...
To my previous comment, this does not seem to be working for my `.github` repository, but does work for other repositories in the same org, even through [extensible configuration](https://github.com/probot/probot-config#an-opt-in-pattern) used...
I force-pushed a few attempts to my `.github` repo, as you can see here and I’m pretty sure I tried without the context (along other combinations), but honestly, I may...
@travi My original config works on a new org, both with/without the required checks context. See [this example without the context](https://github.com/coglinc/.github/commit/a5f6be698598573595b4a9baf40e55ea865ab001) and [this one with the context](https://github.com/coglinc/.github/commit/e46abfedf911e90917284cfd5395891f3672f792). Both configurations are...
@SamuelCabralCruz `required_signatures` _should_ work. See: https://github.com/probot/settings/issues/220#issuecomment-613741695 I did use it on a recent greenfield project and was working fine, BUT I do have occurrences of branch protection not being applied...
You can always provide a `.npmrc` file, with the `registry` and `_auth` properties set to whatever fits your case. If you need the `_auth` property to be injectable, set it...
Related to this, it would be nice if we could specify the Shorebird version installed by this action. Bonus points for supporting reading version from `.tool-versions`. Just been hit by...
@eseidel For some context on the above request: - we use asdf to manage our tooling dependencies, including Shorebird (we thus have a `.tool-versions` that specifies the Shorebird version we...
@vincenzopalazzo any chance of getting this merged and released quickly if I fork this PR and submit an updated version? This is creating an unnecessary roadblock for projects that use...