Michał Knapik

Results 21 comments of Michał Knapik

:+1: for merging. It'll be very useful.

@subnut Controlling source volume works for me when repeating the module twice. `volume.sh` is a custom script which is a wrapper for `pamixer`. ```json { ... "pulseaudio#input": { "format-source": "",...

@mbj Is this feature still on the roadmap? I wanted to integrate mutant with https://github.com/prontolabs/pronto so I need some kind of structured report to pass messages to the tool.

@mbj Thanks for fast answer. I'm developing pronto-mutant for educational purposes so I'm not interested in hiring anyone. I was thinking about implementing a reporter as part as a new...

First you have to setup new project, then add OAuth credentials. Here are a couple of screenshots: ![Screenshot-2021-03-13-205744](https://user-images.githubusercontent.com/249141/111042676-d6b5a780-843e-11eb-93f1-fa73c30d1c9c.png) ![Screenshot-2021-03-13-205542](https://user-images.githubusercontent.com/249141/111042649-aff77100-843e-11eb-8ac8-5465a4f14eac.png) ![Screenshot-2021-03-13-205606](https://user-images.githubusercontent.com/249141/111042651-b2f26180-843e-11eb-9ba9-8f598598202a.png)

Is there will to merge this PR? Looks like JSON API specification supports such format and it would be useful for our project as well. I'm willing to write more...

Assuming you're talking about GitHub checks on pull request, wouldn't ignoring the check and mergin be enough? Or is it about pronto exit code on CI?

@mmozuras I run into that issue while working on a new runner for https://github.com/mbj/mutant. AFAIK the tool does not provide any configuration via env vars nor config files so I'm...

@doomspork @mmozuras Thanks for your feedback! I'll figure out what works best for my case.

So the use case is: `PULL_REQUEST_ID` env var is not set, branch exists both locally and remotely but no PR is submitted for that branch? Returning informative message sounds reasonable...