April "after the Fool's" 2023 in Darker: Addressing GitHub Actions and VSCode formatting issues #702
akaihola
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This month saw some important bug fixes and discussions around Darker's integration with other tools. We addressed an issue with the GitHub Actions workflow where the commit-range action wasn't working correctly in release branches (PR #486). This fix resolves problems reported in issues #489 and #485, ensuring smoother CI/CD processes for projects using Darker.
A community member reported an issue with Darker not formatting code in VSCode when isort was enabled (issue #488). While the problem couldn't be consistently reproduced and was eventually closed, it sparked a discussion about potential interactions between Darker, isort, and VSCode's formatting settings.
On the technical side, we encountered and resolved a bug related to Git subprocess calls when dealing with repositories containing a large number of files, even if they were gitignored (issue #490). This fix improves Darker's performance and reliability when working with complex project structures.
Get involved!
As always, we appreciate the community's involvement in reporting issues and submitting pull requests. If you'd like to contribute, there are several open issues and pull requests that could use your attention
Beta Was this translation helpful? Give feedback.
All reactions