-
```
If I change the arguments to a Gyp action, the action does not get re-run when
building the Gyp file with MS Visual Studio.
Here is an example Gyp file that reproduces the problem:
{
'include…
-
# Problem
Current GitHub API has endpoints that are suitable for most use cases but with protected branches new kind of functionality becomes reasonable: bots. Bots could be used to various things:
-…
-
```
If I change the arguments to a Gyp action, the action does not get re-run when
building the Gyp file with MS Visual Studio.
Here is an example Gyp file that reproduces the problem:
{
'include…
-
```
If I change the arguments to a Gyp action, the action does not get re-run when
building the Gyp file with MS Visual Studio.
Here is an example Gyp file that reproduces the problem:
{
'include…
-
```
If I change the arguments to a Gyp action, the action does not get re-run when
building the Gyp file with MS Visual Studio.
Here is an example Gyp file that reproduces the problem:
{
'include…
-
```
If I change the arguments to a Gyp action, the action does not get re-run when
building the Gyp file with MS Visual Studio.
Here is an example Gyp file that reproduces the problem:
{
'include…
-
```
If I change the arguments to a Gyp action, the action does not get re-run when
building the Gyp file with MS Visual Studio.
Here is an example Gyp file that reproduces the problem:
{
'include…
-
```
If I change the arguments to a Gyp action, the action does not get re-run when
building the Gyp file with MS Visual Studio.
Here is an example Gyp file that reproduces the problem:
{
'include…
-
```
If I change the arguments to a Gyp action, the action does not get re-run when
building the Gyp file with MS Visual Studio.
Here is an example Gyp file that reproduces the problem:
{
'include…
-
I want to cover the use-cases when a `bot` has to notify `user` about "unavailable api" or any other typed Error (not just Box\ )
So, now when an error occurs it's just logged. For simple cases it'…