chore: Format all json files to use 2 spaces#91
Conversation
|
📊 Survey: Please help us track internal AI adoption. This is not for evaluation, only for metrics. You can update this anytime before merge.
🧑💻 If AI was used, what was it mainly used for?
Thank you in advance for your feedback.💙🙏🎉 |
There was a problem hiding this comment.
The PR is a straightforward reformatting of three Renovate config files from 4-space indentation to 2-space indentation, with no semantic changes. The reformatting itself looks correct, but I flagged three pre-existing typos in security.json5 ("apporval" and "sverity" ×2) that were carried over and are worth correcting while the file is already being touched.
PR Bot Information
Version: 1.20.43
- Correlation ID:
85beaee1-cf2b-49fe-bc0e-0decf122b46e - File Content Strategy: Full file content
- Event Trigger:
pull_request.opened - LLM:
anthropic--claude-4.6-sonnet
Reformat Renovate Preset JSON Files to Use 2-Space Indentation
Chore
🔧 Reformatted all Renovate preset JSON/JSON5 configuration files to use consistent 2-space indentation instead of 4-space indentation. No functional changes were made.
Changes
renovate-presets/automerge.json5: Reformatted from 4-space to 2-space indentation; condensed single-element arrays to inline format (e.g.,"schedule"and"automergeSchedule").renovate-presets/branch-merge.json: Reformatted from 4-space to 2-space indentation; condensedmatchUpdateTypesandautomergeSchedulearrays to inline format.renovate-presets/security.json5: Reformatted from 4-space to 2-space indentation; all keys and values remain unchanged.PR Bot Information
Version:
1.20.43anthropic--claude-4.6-sonnetpull_request.opened85beaee1-cf2b-49fe-bc0e-0decf122b46e