-
Updated
Oct 2, 2020 - Python
merge
Here are 531 public repositories matching this topic...
-
Updated
Oct 25, 2020 - Go
-
Updated
Nov 2, 2020 - C++
-
Updated
Oct 18, 2020 - Go
-
Updated
Sep 5, 2020 - TypeScript
-
Updated
Oct 9, 2020 - JavaScript
-
Updated
Apr 19, 2020 - Go
It's perfectly possible that one of stdout/stderr is redirected to terminal (sys.X.isatty()=True
), and the the other is not. As for now, we check isatty
for stdout, and apply this setting to stderr as well.
-
Updated
Jul 6, 2020 - PHP
-
Updated
Jun 8, 2020 - JavaScript
-
Updated
Sep 16, 2020 - C#
-
Updated
Jul 29, 2020 - JavaScript
-
Updated
Apr 16, 2017 - AutoHotkey
-
Updated
Jul 31, 2020 - Elixir
-
Updated
Jul 9, 2020 - JavaScript
-
Updated
Jul 13, 2019 - JavaScript
-
Updated
Jun 22, 2020 - PHP
-
Updated
Oct 31, 2020 - Shell
-
Updated
Sep 10, 2019 - Shell
Improve this page
Add a description, image, and links to the merge topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the merge topic, visit your repo's landing page and select "manage topics."
Hello,
recently we noticed that when commenting on an issue
@Mergifyio backport branch-xx
will create the PR even in presence of conflicts.Is it possible to change the default behaviour to avoid creating the PR if there are conflicts in the configuration file?
Or we'll have to always add
--ignore-conflicts=false
manually?Looking at the documentation we can't find a way to set default