yanghua commented on a change in pull request #1896:
URL: https://github.com/apache/hudi/pull/1896#discussion_r463960642



##########
File path: docs/_pages/contributing.md
##########
@@ -24,11 +24,23 @@ To contribute code, you need
 
 To contribute, you would need to do the following
  
- - Fork the Hudi code on Github & then clone your own fork locally. Once 
cloned, we recommend building as per instructions on 
[quickstart](/docs/quick-start-guide.html)
- - [Recommended] We have embraced the code style largely based on [google 
format](https://google.github.io/styleguide/javaguide.html). Please setup your 
IDE with style files from 
[here](https://github.com/apache/hudi/tree/master/style).
-These instructions have been tested on IntelliJ. 
- - [Recommended] Set up the [Save Action 
Plugin](https://plugins.jetbrains.com/plugin/7642-save-actions) to auto format 
& organize imports on save. The Maven Compilation life-cycle will fail if there 
are checkstyle violations.
- - [Optional] If needed, add spark jars to the classpath of your module in 
Intellij by following the steps from 
[here](https://stackoverflow.com/questions/1051640/correct-way-to-add-external-jars-lib-jar-to-an-intellij-idea-project).
 
+- Fork the Hudi code on Github & then clone your own fork locally. Once 
cloned, we recommend building as per instructions on 
[quickstart](/docs/quick-start-guide.html)
+
+- \[Recommended\] We have embraced the code style largely based on [google 
format](https://google.github.io/styleguide/javaguide.html). Please setup your 
IDE with style files from [\<project 
root\>/style/](https://github.com/apache/hudi/tree/master/style). These 
instructions have been tested on IntelliJ.

Review comment:
       Why we should add `\` before `[` and `]`?




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to