This is an automated email from the ASF dual-hosted git repository.

mimaison pushed a commit to branch markdown
in repository https://gitbox.apache.org/repos/asf/kafka-site.git


The following commit(s) were added to refs/heads/markdown by this push:
     new 26f8bbbcf MINOR: Fix link to coding guidelines (#795)
26f8bbbcf is described below

commit 26f8bbbcf4d5e4a982828e58f73cc8c3c7a920a9
Author: ChiaYi C. <[email protected]>
AuthorDate: Thu Feb 5 23:08:36 2026 +0900

    MINOR: Fix link to coding guidelines (#795)
    
    
    Reviewers: Mickael Maison <[email protected]>
---
 content/en/community/developer.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/en/community/developer.md 
b/content/en/community/developer.md
index b279ed16e..39d11440d 100644
--- a/content/en/community/developer.md
+++ b/content/en/community/developer.md
@@ -66,7 +66,7 @@ To submit a change for inclusion, please do the following:
 
   * If the change is non-trivial please include some unit tests that cover the 
new functionality.
   * If you are introducing a completely new feature or API it is a good idea 
to start a wiki and get consensus on the basic design first.
-  * Make sure you have observed the recommendations in the [style 
guide](coding-guide.html).
+  * Make sure you have observed the recommendations in the [style 
guide](#coding-guidelines).
   * Follow the detailed instructions in [Contributing Code 
Changes](https://cwiki.apache.org/confluence/display/KAFKA/Contributing+Code+Changes).
   * Note that if the change is related to user-facing protocols / interface / 
configs, etc, you need to make the corresponding change on the documentation as 
well. For wiki page changes feel free to edit the page content directly (you 
may need to contact us to get the permission first if it is your first time to 
edit on wiki); website docs live in the code repo under `docs` so that changes 
to that can be done in the same PR as changes to the code. Website doc change 
instructions are give [...]
   * It is our job to follow up on patches in a timely fashion. [Nag 
us](mailto:[email protected]) if we aren't doing our job (sometimes we drop 
things).

Reply via email to