Skip to content

Commit 04d29dc

Browse files
authored
Merge branch 'main' into scheduled-workflow-tests
2 parents 7b2d060 + b381339 commit 04d29dc

3 files changed

Lines changed: 28 additions & 2 deletions

File tree

content/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,11 @@ topics:
1111
- repositories
1212
---
1313

14-
If you allow auto-merge for pull requests in your repository, people can configure individual pull requests in the repository to merge automatically when all merge requirements are met. For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)."
14+
### About auto-merge
15+
16+
If you allow auto-merge for pull requests in your repository, people with write permissions can configure individual pull requests in the repository to merge automatically when all merge requirements are met. {% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}If someone who does not have write permissions pushes changes to a pull request that has auto-merge enabled, auto-merge will be disabled for that pull request. {% endif %}For more information, see "[Automatically merging a pull request](/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request)."
17+
18+
### Managing auto-merge
1519

1620
{% data reusables.repositories.navigate-to-repo %}
1721
{% data reusables.repositories.sidebar-settings %}

content/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,9 @@ topics:
1414

1515
If you enable auto-merge for a pull request, the pull request will merge automatically when all required reviews are met and status checks have passed. Auto-merge prevents you from waiting around for requirements to be met, so you can move on to other tasks.
1616

17-
Before you can use auto-merge with a pull request, auto-merge must be enabled for the repository. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)."
17+
Before you can use auto-merge with a pull request, auto-merge must be enabled for the repository. For more information, see "[Managing auto-merge for pull requests in your repository](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository)."{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@next" or currentVersion ver_gt "enterprise-server@3.1" %}
18+
19+
After you enable auto-merge for a pull request, if someone who does not have write permissions to the repository pushes new changes to the head branch or switches the base branch of the pull request, auto-merge will be disabled. For example, if a maintainer enables auto-merge for a pull request from a fork, auto-merge will be disabled after a contributor pushes new changes to the pull request.{% endif %}
1820

1921
You can provide feedback about auto-merge by [contacting us](https://support.github.com/contact/feedback?category=prs-and-code-review&subject=Pull%20request%20auto-merge%20feedback).
2022

lib/redis/create-client.js

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,10 +42,30 @@ module.exports = function createClient (options = {}) {
4242
}
4343
},
4444

45+
// Any running command that is unfulfilled when a connection is lost should
46+
// NOT be retried after the connection has been reestablished.
47+
retry_unfulfilled_commands: false,
48+
49+
// If we failed to send a new command during a disconnection, do NOT
50+
// enqueue it to send later after the connection has been [re-]established.
51+
// This is also critical to preventing a backend pile-up!
52+
enable_offline_queue: false,
53+
4554
// Expand whatever other options and overrides were provided
4655
...options
4756
})
4857

58+
// Handle connection errors to prevent killing the Node.js process
59+
client.on('error', (connectError) => {
60+
try {
61+
// Forcibly close the connection to the Redis server.
62+
// Allow all still running commands to silently fail immediately.
63+
client.end(false)
64+
} catch (disconnectError) {
65+
// Swallow any failure
66+
}
67+
})
68+
4969
// If a `name` was provided, use it in the prefix for logging event messages
5070
const logPrefix = '[redis' + (name ? ` (${name})` : '') + ']'
5171

0 commit comments

Comments
 (0)