From ad69e390e6bae2e47080ddc7c5552509eb0f8cb3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20K=C3=B6nig?= Date: Fri, 17 Apr 2026 16:35:05 +0200 Subject: [PATCH 1/3] Refine merge policy --- CONTRIBUTING.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 08a273f..6afe010 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -41,15 +41,18 @@ Thank you for contributing! This blog is a simple, engineer-driven space for tec 5. Create a [blog post folder structure](#blog-post-folder-structure). 4. Ready to review? 1. Put it "in review" - 2. Create a PR and link to issue with #{issue-number} + 2. Create a Pull Request and link to issue with #{issue-number} 3. Request feedback from somebody 4. Update based on feedback where helpful + 5. Request from [@bbv-blogger-admin team](https://github.com/orgs/bbvch/teams/bbv-blog-admin) approval in Pull Request 5. Ready to publish? - 1. Request from [@bbv-blogger-admin team](https://github.com/orgs/bbvch/teams/bbv-blog-admin) approval in PR - 2. When approved, you can merge + 1. When approved, wait for a publishing date + 2. When the publishing date is clear, change the blog path and the frontmatter accordingly + 3. The merge is done by the [@bbv-blogger-admin team](https://github.com/orgs/bbvch/teams/bbv-blog-admin) except you are notified otherwise. 6. Congrats, you published your post! - 1. [Share it widely](#cross-posting). - 2. Engage with readers in the comments. + 1. A few minutes are the merge, your post will be online. + 2. [Share it widely](#cross-posting). + 3. Engage with readers in the comments. ### Blog post folder structure From e6b68257693672553fb371007eab8eafded6d7f4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20K=C3=B6nig?= Date: Thu, 23 Apr 2026 09:10:56 +0200 Subject: [PATCH 2/3] Fix typo --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6afe010..754e2b5 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -50,7 +50,7 @@ Thank you for contributing! This blog is a simple, engineer-driven space for tec 2. When the publishing date is clear, change the blog path and the frontmatter accordingly 3. The merge is done by the [@bbv-blogger-admin team](https://github.com/orgs/bbvch/teams/bbv-blog-admin) except you are notified otherwise. 6. Congrats, you published your post! - 1. A few minutes are the merge, your post will be online. + 1. A few minutes after the merge, your post will be online. 2. [Share it widely](#cross-posting). 3. Engage with readers in the comments. From 07a3e1974c364a88a0b3690c0f901fe8dd5d02e4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20K=C3=B6nig?= Date: Mon, 27 Apr 2026 10:57:38 +0200 Subject: [PATCH 3/3] Be more specific about who will give the publish date --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 754e2b5..fd8ca8c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -46,8 +46,8 @@ Thank you for contributing! This blog is a simple, engineer-driven space for tec 4. Update based on feedback where helpful 5. Request from [@bbv-blogger-admin team](https://github.com/orgs/bbvch/teams/bbv-blog-admin) approval in Pull Request 5. Ready to publish? - 1. When approved, wait for a publishing date - 2. When the publishing date is clear, change the blog path and the frontmatter accordingly + 1. When approved, wait for the blog administrator to set a publishing date. + 2. When the publishing date is set, change the blog path and the frontmatter accordingly. 3. The merge is done by the [@bbv-blogger-admin team](https://github.com/orgs/bbvch/teams/bbv-blog-admin) except you are notified otherwise. 6. Congrats, you published your post! 1. A few minutes after the merge, your post will be online.