jbampton opened a new pull request, #7562:
URL: https://github.com/apache/cloudstack/pull/7562

   ### Description
   
   This PR adds a simple `EditorConfig` file. I used only three settings to 
start with.  
   
   Lots of great projects already use EditorConfig:
   
   https://github.com/editorconfig/editorconfig/wiki/Projects-Using-EditorConfig
   
   And you can see how Apache Airflow does it:
   
   https://github.com/apache/airflow/blob/main/.editorconfig
   
   From the official site:
   
   "EditorConfig helps maintain consistent coding styles for multiple 
developers working on the same project across various editors and IDEs. The 
EditorConfig project consists of a file format for defining coding styles and a 
collection of text editor plugins that enable editors to read the file format 
and adhere to defined styles. EditorConfig files are easily readable and they 
work nicely with version control systems."
   
   https://editorconfig.org/
   
   A lot of editors already come bundled with support: 
https://editorconfig.org/#pre-installed
   
   Some editors require you to download a plugin: 
https://editorconfig.org/#download
   
   <!--- Describe your changes in DETAIL - And how has behaviour functionally 
changed. -->
   
   <!-- For new features, provide link to FS, dev ML discussion etc. -->
   <!-- In case of bug fix, the expected and actual behaviours, steps to 
reproduce. -->
   
   <!-- When "Fixes: #<id>" is specified, the issue/PR will automatically be 
closed when this PR gets merged -->
   <!-- For addressing multiple issues/PRs, use multiple "Fixes: #<id>" -->
   <!-- Fixes: # -->
   
   <!--- 
*********************************************************************************
 -->
   <!--- NOTE: AUTOMATATION USES THE DESCRIPTIONS TO SET LABELS AND PRODUCE 
DOCUMENTATION. -->
   <!--- PLEASE PUT AN 'X' in only **ONE** box -->
   <!--- 
*********************************************************************************
 -->
   
   ### Types of changes
   
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to change)
   - [X] New feature (non-breaking change which adds functionality)
   - [ ] Bug fix (non-breaking change which fixes an issue)
   - [ ] Enhancement (improves an existing feature and functionality)
   - [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
   
   ### Feature/Enhancement Scale or Bug Severity
   
   #### Feature/Enhancement Scale
   
   - [ ] Major
   - [X] Minor
   
   #### Bug Severity
   
   - [ ] BLOCKER
   - [ ] Critical
   - [ ] Major
   - [ ] Minor
   - [X] Trivial
   
   
   ### Screenshots (if appropriate):
   
   
   ### How Has This Been Tested?
   <!-- Please describe in detail how you tested your changes. -->
   <!-- Include details of your testing environment, and the tests you ran to 
-->
   <!-- see how your change affects other areas of the code, etc. -->
   
   
   <!-- Please read the 
[CONTRIBUTING](https://github.com/apache/cloudstack/blob/main/CONTRIBUTING.md) 
document -->
   


-- 
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.

To unsubscribe, e-mail: [email protected]

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

Reply via email to