From dcea86c4a2e77d9f7fa491eacba72af0a68632c6 Mon Sep 17 00:00:00 2001 From: Jonah Graham Date: Wed, 9 Nov 2022 09:51:22 -0500 Subject: [PATCH] Fix old link to IP log The new link is where the old link redirected to --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d989140028f..b8bcaf0564f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -87,7 +87,7 @@ These are the steps that a committer should undertake for all Pull Requests. 1. Set the milestone field to the release in which patch would be applied, If it is applied in two branches set milestone to maintenance branch 2. Code inspect and test and the patch -3. If the patch is > 1,000 lines and from a non-committer, it must be submitted for IP review, i.e. CQ in IPZilla. See [IP Log](https://wiki.eclipse.org/Development_Resources/Automatic_IP_Log) +3. If the patch is > 1,000 lines and from a non-committer, it must be submitted for IP review, i.e. CQ in IPZilla. See [IP Log](https://www.eclipse.org/projects/handbook/#ip-iplog) 4. Merge the Pull Request. Do so while keeping a clean history for CDT - Use "Rebase and Merge" when the Pull Request has multiple commits separated in a logical fashion. - Use "Squash and Merge" when merging the PR, especially one where subsequent commits are simply review fixes.