automerge
Here are 15 public repositories matching this topic...
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
-
Updated
Apr 19, 2021 - TypeScript
When opening a Draft Pull Request the world driven message is commented with a time to merge.
This message should only happen on non Draft Pull Request creation, or changing the status from Draft to Open.
-
Updated
Apr 19, 2021 - TypeScript
-
Updated
Apr 27, 2021 - TypeScript
-
Updated
Apr 28, 2021 - TypeScript
-
Updated
Apr 26, 2021 - TypeScript
-
Updated
Nov 19, 2020 - TypeScript
-
Updated
Apr 19, 2021 - TypeScript
-
Updated
Apr 28, 2021 - PHP
-
Updated
Feb 28, 2020 - C#
-
Updated
Apr 28, 2021 - JavaScript
Improve this page
Add a description, image, and links to the automerge topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the automerge topic, visit your repo's landing page and select "manage topics."
Hi, thank you for making a great plugin.
We previously created our own plugin for our company based on this repository.
I'd like to share some points we noticed when we created it. We deleted it in the end because we no longer need collaborative editing features, though.
This is not an issue, so you can close this “issue” after you read it. I just want to pay you back.
I'm sorry I haven't