Abdullah Alaqeel

I would suggest we first create a transparent CI/CD process requiring at least 2 devs to approve PRs, and prevent any individual maintainer from uploading release archives manually.Perhaps create multiple...

@hramezani totally not related

I can do the integration but I want to run it by you first so my effort isn’t lost if this won’t be merged.The idea is to use the advanced...

We could have it as an optional dependency. If people wants it, they can install it with `pip install django-auditlog[filters]` or something like that.

I think this will have to be on the back burner for now. I have other ideas for this project that I think are more important/helpful to the users.

@hramezani Sorry I didn't get around to the pr. The issue is that when we're calling `.get_fields()` in [diff.py](https://github.com/jazzband/django-auditlog/blob/master/auditlog/diff.py#L51), we're getting the auto created fields. Maybe we can exclude them...

Actually, I'm having trouble wrapping my mind around how we'd handle foreign keys (user and contenttype) when we're using multiple databases. Any ideas?

Can you elaborate more? Do you have a working example?

you can probably add this to your model ```python class MyModel(models.Model): __audit_log_change_reason: str = "" @property def audit_log_change_reason(self) -> str: return self.__audit_log_change_reason @audit_log_change_reason.setter def audit_log_change_reason(self, value: str) -> None: self.__audit_log_change_reason...

@alieh-rymasheuski in your suggestion, would the steps be separate versions or one version but controller by a conf variable?