-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Various fixes #50
Various fixes #50
Conversation
updates: - [github.com/asottile/pyupgrade: v3.3.1 → v3.3.2](asottile/pyupgrade@v3.3.1...v3.3.2)
updates: - [github.com/charliermarsh/ruff-pre-commit: v0.0.262 → v0.0.263](astral-sh/ruff-pre-commit@v0.0.262...v0.0.263)
updates: - [github.com/charliermarsh/ruff-pre-commit: v0.0.263 → v0.0.265](astral-sh/ruff-pre-commit@v0.0.263...v0.0.265) - [github.com/asottile/pyupgrade: v3.3.2 → v3.4.0](asottile/pyupgrade@v3.3.2...v3.4.0)
updates: - [github.com/charliermarsh/ruff-pre-commit: v0.0.265 → v0.0.267](astral-sh/ruff-pre-commit@v0.0.265...v0.0.267)
Improve display of options (split line)
(contains dark theme-related fixes)
Oops, I thought that develop & feature/django42 didn't have so many different commits, including your recent commits on develop. What should we do? Is the feature/django42 branch the one that will be used for the release of the next version? Here's a screenshot of the dialog on my branch: Notice the fixed "search icon", and the "forced" light theme (released in django-ckeditor 6.1.1) :) |
@corentinbettiol You can cherry-pick your commits on a fresh branch from |
See #57 for the cherry-picked commits :) |
Description
Describe:
Checklist
inv lint
changes
file included (see docs)