From 8394e3169cafd8579c10545e7feff83c20122314 Mon Sep 17 00:00:00 2001 From: Dongsu Park Date: Fri, 6 May 2022 12:18:05 +0200 Subject: [PATCH] changelog: use a specific project name in the example To be able to distinguish changelog entries from each other, we should write a specific project name, e.g. portage-stable, instead of `PR`. Changelog entries with a simple `PR` usually cause so much additional rework when doing actual releases. --- .../src/third_party/portage-stable/changelog/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sdk_container/src/third_party/portage-stable/changelog/README.md b/sdk_container/src/third_party/portage-stable/changelog/README.md index cf4aaf46de..83c1f312e2 100644 --- a/sdk_container/src/third_party/portage-stable/changelog/README.md +++ b/sdk_container/src/third_party/portage-stable/changelog/README.md @@ -15,7 +15,7 @@ The file should contain a markdown bullet point entry (`- TEXT...`). Example for the bugfix section: ``` -- The Torcx profile `docker-1.12-no` got fixed to reference the current Docker version instead of 19.03 which wasn't found on the image, causing Torcx to fail to provide Docker [PR#1456](https://github.com/flatcar-linux/coreos-overlay/pull/1456) +- The Torcx profile `docker-1.12-no` got fixed to reference the current Docker version instead of 19.03 which wasn't found on the image, causing Torcx to fail to provide Docker [portage-stable#1456](https://github.com/flatcar-linux/portage-stable/pull/1456) ``` The contents of the file should describe the changes in a concise manner,