From 62862705a56e5222d4529cf87263e55f8ffe6c5e Mon Sep 17 00:00:00 2001 From: Julien Danjou Date: Sat, 30 Sep 2023 22:58:46 +0200 Subject: [PATCH 1/5] docs(integrations): fix Jenkins link Change-Id: Ifd1df7b3f6be0d93dce097960262f16a18397b8c --- src/content/integrations/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/integrations/index.mdx b/src/content/integrations/index.mdx index a3c864c108..9a3ebaf10e 100644 --- a/src/content/integrations/index.mdx +++ b/src/content/integrations/index.mdx @@ -25,7 +25,7 @@ import { TbBike } from 'react-icons/tb'; } /> Date: Sat, 30 Sep 2023 22:59:41 +0200 Subject: [PATCH 2/5] docs(mq): fix link to spec checks Change-Id: I57b64609455c160734f99aca60202caf863ca6bd --- src/content/workflow/actions/queue.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/workflow/actions/queue.mdx b/src/content/workflow/actions/queue.mdx index 185c970b46..3439070276 100644 --- a/src/content/workflow/actions/queue.mdx +++ b/src/content/workflow/actions/queue.mdx @@ -10,7 +10,7 @@ queue](/merge-queue/intro). By placing pull requests in a queue, you can make sure they are up-to-date and control their processing based on their priority. Each queue can also have its own configuration for [speculative -checks](/merge-queue/speculative), [batches](/merge-queue/batches), etc. +checks](/merge-queue/speculative-checks), [batches](/merge-queue/batches), etc. ## Parameters From 761a952bc8ae6060f0ecfe0e2dd280169aa70275 Mon Sep 17 00:00:00 2001 From: Julien Danjou Date: Sat, 30 Sep 2023 23:01:54 +0200 Subject: [PATCH 3/5] docs(security): fix mailto mail Change-Id: I5433906bc1debe492b1c822afa2e8f5a79b2c8b4 --- src/content/security.mdx | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/content/security.mdx b/src/content/security.mdx index 59b4c0236e..98d7e4e613 100644 --- a/src/content/security.mdx +++ b/src/content/security.mdx @@ -40,8 +40,9 @@ security-related issue on our platform, we appreciate you disclosing the issue to us responsibly, and thank you for your time and expertise. If you want to participate in our private Bug Bounty Program, send us an email -at security@mergify.com -with your HackerOne username or the email you want an invitation for. +at security@mergify.com with your +HackerOne username or the email you want an invitation for. ## Required Permissions From 496149665c7ef72181caab7929190555f33e9255 Mon Sep 17 00:00:00 2001 From: Julien Danjou Date: Sat, 30 Sep 2023 23:06:04 +0200 Subject: [PATCH 4/5] docs(assign): fix link to data type Change-Id: I60247d29e41b0e157c7d979c127968c25811aa98 --- src/content/workflow/actions/assign.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/workflow/actions/assign.mdx b/src/content/workflow/actions/assign.mdx index f1ccb2fd38..ed4f56915c 100644 --- a/src/content/workflow/actions/assign.mdx +++ b/src/content/workflow/actions/assign.mdx @@ -18,8 +18,8 @@ pull requests that require their attention. As the list of users in `add_users` or `remove_users` is based on -[templates](data-type#template), you can use, e.g., `{{author}}` to assign the -pull request to its author. +[templates](/configuration/data-type#template), you can use, e.g., `{{author}}` +to assign the pull request to its author. Make sure the users you specify in the assign action have the necessary From a50cab979eee498735cc2cbea8a124359dc87e11 Mon Sep 17 00:00:00 2001 From: Julien Danjou Date: Sat, 30 Sep 2023 23:06:37 +0200 Subject: [PATCH 5/5] docs(rush): fix wrong relative link Change-Id: Ib01a94e00bbd7b06011e67bbe9a38b1b36f85d1b --- src/content/integrations/rush.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/integrations/rush.mdx b/src/content/integrations/rush.mdx index a77daa0794..5eb2ecb4fa 100644 --- a/src/content/integrations/rush.mdx +++ b/src/content/integrations/rush.mdx @@ -44,8 +44,8 @@ development lifecycle. #### Creating Partitions for Each Project To implement this, we define `partitions` for each sub-project using -[`partition_rules`](merge-queue/partitions/) in our Mergify configuration. Each -partition can then have its specific [`queue_rules`](/merge-queue/setup) +[`partition_rules`](/merge-queue/partitions/) in our Mergify configuration. +Each partition can then have its specific [`queue_rules`](/merge-queue/setup) defining the merge conditions based on each sub-project’s requirements. #### Example Configuration