chore: enhance developer tooling and configuration #894
Conversation
This file contains hidden or 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
Add new hooks for end-of-file fixing and trailing whitespace removal, excluding Markdown files to preserve line breaks. Integrate Prettier for consistent formatting of YAML and JSON files, aligning with .editorconfig settings. Update Ruff version to v0.11.13 for consistency across linting and formatting. Expand exclusion patterns to include node_modules and .venv directories, preventing unnecessary checks in these areas. These changes improve code quality and consistency by automating formatting and ensuring adherence to style guidelines, while also enhancing performance by excluding irrelevant directories.
…ings and file handling Introduce a .gitattributes file to ensure consistent line endings across different operating systems, which helps prevent unnecessary diffs due to line ending differences. Define handling for various file types, including text, binary, and large files, to optimize Git's behavior and improve collaboration. This setup also includes export ignores for specific directories and files, enhancing repository cleanliness and efficiency.
Add an .editorconfig file to enforce consistent coding style across different editors and IDEs. This helps maintain uniform code formatting, making collaboration easier and reducing formatting-related issues. chore: update VSCode settings and extensions for better integration Add EditorConfig extension to recommended VSCode extensions to ensure developers have the necessary tools for consistent code formatting. Update VSCode settings to align with .editorconfig rules, such as setting end-of-line characters, inserting final newlines, and trimming trailing whitespace. This ensures that the development environment is configured to automatically adhere to the project's coding standards.
Ensure consistent formatting across various configuration and workflow files by adjusting indentation, spacing, and quotations. Add missing newlines at the end of files to comply with POSIX standards and improve compatibility with tools that expect newline-terminated files. These changes enhance readability, maintainability, and conformity to best practices, reducing potential issues with file parsing and version control diffs.
…y and adjust print width Exclude the .vscode directory from Prettier formatting to prevent unnecessary formatting of editor-specific settings. Adjust the print width to 80 to enforce shorter line lengths, improving readability, especially for arrays. style(vscode): reformat settings.json for better readability Reformat the "python.analysis.exclude" array in settings.json to have each entry on a new line, enhancing readability and consistency with other JSON formatting practices.
Contributor
Reviewer's GuideThis PR implements cross-editor and cross-platform consistency by introducing editor and Git attributes, integrates Prettier into pre-commit hooks alongside other fixes, standardizes YAML formatting in GitHub Actions workflows, updates VSCode settings and extensions, and applies uniform formatting and newline corrections across various config and documentation files. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
…chema glob pattern Add binary attribute for media files (*.mp4, *.mov, *.avi) to ensure they are treated as binary files. Remove Git LFS configuration for these media files as they are now handled as binary. Correct the glob pattern for Prisma schema files to include all schema files in subdirectories, ensuring consistent line endings. This improves file handling and ensures correct processing of media and schema files.
Deploying tux with
|
| Latest commit: |
0a6a285
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://040c3ecf.tux-afh.pages.dev |
| Branch Preview URL: | https://refactor-dotfiles.tux-afh.pages.dev |
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 PR enhances the developer experience by adding and improving configuration files:
Changes:
.editorconfigfor consistent coding style across editors.gitattributesfor consistent line endings across platforms.vscodedirectory from Prettier formattingBenefits:
Commits:
b9f1019: Update prettier config and VSCode settingsadf75ba: Apply consistent formatting and add missing newlines7e940d6: Add .editorconfig and update VSCode configuration49ae236: Add .gitattributes for consistent line endings19259ca: Update pre-commit hooks configurationNo breaking changes. All changes are focused on developer tooling and code quality improvements.
Summary by Sourcery
Apply consistent formatting and enhance developer tooling by adding new config files, updating pre-commit hooks, and standardizing styles across editors and CI workflows.
Enhancements: