hxuanyu/intellij-sdk-code-samples
1
0
Fork 0
mirror of https://github.com/JetBrains/intellij-sdk-code-samples.git synced 2025-07-30 10:17:50 +08:00
Code Issues Packages Projects Releases Wiki Activity

intellij_coding_guidelines.md: clarifications from feedback (IJSDK-1456)

Browse Source
This commit is contained in:
Yann Cébron 2022-06-30 09:58:37 +02:00
parent d536a22fe3
commit e3d6328421
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
topics/basics/intellij_coding_guidelines.md
View File

@ -6,8 +6,8 @@ If you are writing code that you would like to contribute to the IntelliJ Platfo
## Following the Latest Source Code
If you submit patches, we strongly recommend building your patches against the latest version of the code from the Git repository.
The easiest way to do so is to clone the JetBrains Git repository, track your work in Git, and create patches using the "git format-patch" command.
If you submit patches, we strongly recommend building your patches against the latest version of the code from the [intellij-community Git repository](intellij_platform.md#open-source).
The easiest way to do so is to clone the repository, track your work in Git, and provide your changes as described in [](platform_contributions.md#submit-a-patch).
## General Architectural Principles
@ -58,4 +58,4 @@ The ideal pull request would contain one commit with everything needed to fix th
The best would be to commit early, but then to squash all commits into one with a descriptive commit message.
Sometimes several commits for a single issue are also acceptable, but each of these should be self-contained "steps" to solve the problem.
Sometimes several commits for a single issue are also acceptable, but each of these should be self-contained "steps" to solve the problem.