Buddhike de Silva
Buddhike de Silva
+1 to this feature request. I have a scenario where my container uses two ports to segregate two type of users. e.g. Port A is used by consumers to access...
@sindresorhus Is this PR accepted?
Sounds reasonable. Not sure if you have seen this, but there's already a feature to do the reverse. https://github.com/mbtproject/mbt/blob/master/doc/mbt_build_commit.md (See `--name` and `--fuzzy` options) What do you think about `--exclude`...
Thanks for the detailed explanation. I've been giving some thought into this and definitely think this feature should go into the product. May be the details of how to handle...
@dustyhorizon Sorry, re-reading this thread clarified your use case. > I think further consideration is required so that this feature could benefit most pipelines without requiring some sort of funny...
@dustyhorizon Thanks for further input. This is a reasonable request and I've already marked it as an enhancement (which is an indication that this would be added in a future...
I guess the proposed structure for user defined commands would be: ``` commands: name: foo: - cmd: foo.sh args: [a, b] os: [linux, darwin] - cmd: powershell args: [-file, foo.ps1]...
Thanks @sergey-ostapenko Whilst I was working on the first implementation of `run-in` command, I thought about making it more general purpose like this: ``` mbt run-in branch ./custom.sh arg1 arg2...
Thanks for reporting this issue @swaroopbhatk. Just curious, does this happen only when you have one commit in your repo?
Thanks for reporting this issue. 1. Long path is definitely going to be an issue. Which version of Windows are you using? I will get back to you on this...