Add CustomLogEntry model support and update tests:

[mostafaeftekharizadeh]

• Added support for CustomLogEntry data model to extend django-auditlog capabilities

• Updated existing test cases to align with new model structure and data handling logic

• Added new test cases to validate CustomLogEntry behavior, model registration, and signal handling

• Ensured backward compatibility with existing LogEntry model where applicable

[codecov]

Codecov Report

❌ Patch coverage is 98.50746% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 95.92%. Comparing base (0e58a9d) to head (1889387).

Files with missing lines	Patch %	Lines
auditlog/context.py	96.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #764      +/-   ##
==========================================
+ Coverage   95.85%   95.92%   +0.06%     
==========================================
  Files          35       35              
  Lines        1207     1250      +43     
==========================================
+ Hits         1157     1199      +42     
- Misses         50       51       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[mostafaeftekharizadeh]

Hi @2ykwang , could you please take a look at this PR when you have a moment? Your feedback would be really helpful. Thanks in advance!

[2ykwang]

Thanks for the PR! @mostafaeftekharizadeh

I’ll review it within this week.
In the meantime, could you please check the failing tests on MySQL and PostgreSQL?
Also, it looks like we’ll need updates to the CHANGELOG and related documentation for these changes.

[hramezani]

Lint is failing in CI for Python 3.10. @mostafaeftekharizadeh could you figure out what the problem is?

@2ykwang Please review the PR when you have time.

[mostafaeftekharizadeh]

Lint is failing in CI for Python 3.10. @mostafaeftekharizadeh could you figure out what the problem is?

@2ykwang Please review the PR when you have time.

Linter issue resolved.

[2ykwang]

@mostafaeftekharizadeh

do we need to run the full test suite for both LogEntry and CustomLogEntry?

I’m worried this might unnecessarily increase test runtime. maybe we could just add specific tests for the custom model instead?

[mostafaeftekharizadeh]

@mostafaeftekharizadeh

do we need to run the full test suite for both LogEntry and CustomLogEntry?

I’m worried this might unnecessarily increase test runtime. maybe we could just add specific tests for the custom model instead?

Given the large amount of changes, I suggest running the full test suite for CustomLogEntry at least once, for example, on the latest LTS version.

[2ykwang]

Given the large amount of changes, I suggest running the full test suite for CustomLogEntry at least once, for example, on the latest LTS version.

What if we just add one custom model test matrix instead? For example:

py312-customlogmodel-django52

[2ykwang]

@hramezani could you take a look as well?

[hramezani]

Given the large amount of changes, I suggest running the full test suite for CustomLogEntry at least once, for example, on the latest LTS version.

What if we just add one custom model test matrix instead? For example:

py312-customlogmodel-django52

Agree, let's add only one custom model test to the matrix

[hramezani]

Thanks @mostafaeftekharizadeh for continuing on this PR.
Please address the above comments when you have time.

[mostafaeftekharizadeh]

Thanks @mostafaeftekharizadeh for continuing on this PR. Please address the above comments when you have time.

Done.

[2ykwang]

Confirmed. thanks for the contribution! @mostafaeftekharizadeh

[hramezani]

Thanks @mostafaeftekharizadeh for the PR and @2ykwang for the review