Make YAML indent size 2 in .editorconfig
#261
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
benfrankel
approved these changes
Aug 11, 2024
benfrankel
pushed a commit
to benfrankel/bevy_new_2d
that referenced
this pull request
Aug 11, 2024
This makes the indent size for YAML files in `.github/workflows` 2 spaces, as compared to 4. While YAML can technically support any indent size, all of the existing workflows in this repository already use 2 spaces. Furthermore, I had parsing issues in the past using 4 with Github Actions. (I'm unsure if it's a user-error on my part, or some specific of Github Actions.)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This makes the indent size for YAML files in
.github/workflows2 spaces, as compared to 4. While YAML can technically support any indent size, all of the existing workflows in this repository already use 2 spaces. Furthermore, I had parsing issues in the past using 4 with Github Actions. (I'm unsure if it's a user-error on my part, or some specific of Github Actions.)