From 18bdab7a67309b719b7491a3da5d3c174802c5b1 Mon Sep 17 00:00:00 2001 From: Luke Heath Date: Fri, 10 Jan 2025 16:44:27 -0600 Subject: [PATCH] Fixing broken links (#25359) --- handbook/engineering/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/handbook/engineering/README.md b/handbook/engineering/README.md index 253541d5009b..02e4293937df 100644 --- a/handbook/engineering/README.md +++ b/handbook/engineering/README.md @@ -225,7 +225,7 @@ If the PR is a quick fix (i.e. typo) or obvious technical improvement that doesn For PRs that change the product: - Set the PR to draft. -- Thank the contributor for their hard work, explain that all changes to the product go through Fleet's [prioritization process]([TODO link](https://fleetdm.com/handbook/company/product-groups#how-feature-requests-are-prioritized)), and ask them to file a [feature request]([TODO link here](https://github.com/fleetdm/fleet/issues/new?assignees=&labels=%3Aproduct&projects=&template=feature-request.md&title=)). +- Thank the contributor for their hard work, explain that all changes to the product go through Fleet's [prioritization process](https://fleetdm.com/handbook/company/product-groups#how-feature-requests-are-prioritized)), and ask them to file a [feature request](https://github.com/fleetdm/fleet/issues/new?assignees=&labels=%3Aproduct&projects=&template=feature-request.md&title=)) that describe the change their PR is introducing. For PRs that will not be merged: