Lucas Connors

Sorry to revive such an old thread here, but another potential solution would be to define `MARKDOWN_DEUX_DEFAULT_STYLE` in a different module (say `conf/styles.py`) and then import it into `settings.py`. Then...

That's unfortunate that Django 3.1 isn't compatible, but I guess it is to be expected. I don't believe the original author @matthewwithanm maintains this repo anymore. I was the author...

Added a deprecation notice to the README here: https://github.com/matthewwithanm/django-classbasedsettings/pull/25

@guettli My instinct is that the answer will be "no", but I'm not sure how you're imagining using class-based settings in other projects. Is there a specific framework you have...

@richban, for now you should make sure that all models that can show up for content type on this field are models that are registered with admin. I imagine the...

@richban I can reproduce the issue you're talking about. Until just now I hadn't realized that was also a problem. Do you guys think disabling the magnifying glass until a...

FWIW the bug @richban pointed out in this issue has been resolved with the 1.0.9 release.

I don't know about @Evanion's use case, but one use case for requiring features branches to be up-to-date with the main branch before merging is to avoid a situation where...

> ...run the tests on the merge commit prior to pushing... This is how I've parsed the above: Create a feature branch based off of the main branch and open...

Thank you @AArnott for elaborating to help me understand. > 2. Validation runs on the provisionary merge commit created by the (still active) PR... This is the key part I...