Gago
Gago
hey @joshuasimon-taulia, You are 100% right. I will make sure this is added ASAP. Thanks for reporting!
Interesting. I think it makes things more complex to write, but way more clear as well. I like the idea of dividing `triggers` altho, we are gonna need a more...
@cyamonide do you mind investigate how our current rules will look like with this new format? I would hate to do this work without anticipating issues.
We could also do the same with eventJSONPath and split it into include excludes as well. ``` json { "name": "foobar", "action": "comment", "matchers": { "includes": ["*.ts"], "eventJSONPath": { "includes":...
It looks good! It is missing a test that includes the rule I asked you in the issue. Could you share it, so I make sure we don't regress ?...
Hey, @penguin02007 This issue seems to be that your privateKey is not properly generated. Did you follow the steps to create the App in your org? I built a command...
You have a problem in your computer. You are trying to install that package in a place you can't install. EACCESS is that. `sudo npm` or you just do npx...
Means that how you put the secrets in GitHub is not right. Also don't share the token in a public channel. Please edit the comment you left !
I'm just picking this up again. Fixing soon, sorry @gustavkj
Thanks for the detailed steps. I will do this after we release these new functionalities.