fix: import_files command to skip existing files

[misli]

• Fix use of get_or_create to really skip existing files

Description

The import_files command tries to skip existing files, but it always create new one,
because the way it detects the existing one is wrong.

Related resources

Checklist

• I have opened this pull request against master
• I have added or modified the tests when changing logic
• I have followed the conventional commits guidelines to add meaningful information into the changelog
• I have read the contribution guidelines and I have joined #workgroup-pr-review on
  Slack to find a “pr review buddy” who is going to review my pull request.

[codecov]

Codecov Report

Attention: 8 lines in your changes are missing coverage. Please review.

Comparison is base (dbeda3a) 75.22% compared to head (cba2715) 75.09%.
Report is 16 commits behind head on master.

Files	Patch %	Lines
filer/management/commands/import_files.py	0.00%	8 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1420      +/-   ##
==========================================
- Coverage   75.22%   75.09%   -0.14%     
==========================================
  Files          75       75              
  Lines        3455     3461       +6     
  Branches      555      555              
==========================================
  Hits         2599     2599              
- Misses        691      697       +6     
  Partials      165      165              

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

[fsbraun]

Hi @misli ! Thank you for the pull request.

Can you elaborate on the issue? Why are existing files detected wrongly?

From the code I see, you allow to have multiple files with the same name in the same folder but then ignore all of them but the first. To me it is not immediately transparent why this should be the right way to go. But then again, I have not fully understood the issue.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This will now be closed due to inactivity, but feel free to reopen it.