Repository navigation
fix: format group member expiry dates - #1349
Conversation
Codecov Report❌ Patch coverage is
❌ Your project check has failed because the head coverage (68.36%) is below the target coverage (70.00%). You can increase the head coverage or adjust the target coverage.
Additional details and impacted files@@ Coverage Diff @@
## main #1349 +/- ##
==========================================
- Coverage 78.24% 68.36% -9.88%
==========================================
Files 83 83
Lines 4229 4236 +7
==========================================
- Hits 3309 2896 -413
- Misses 920 1340 +420
🚀 New features to boost your workflow:
|
508f328 to
50ea2c7
Compare
|
Added focused unit coverage for the date-expiry call sites to address the Codecov patch coverage failure. Re-ran locally:
|
|
I checked the failing CE acceptance job. The failure is in |
|
CI follow-up: on the latest matrix run, CE now passes and the same unrelated instance-setting failure moved to the EE job. The EE log shows |
|
Thanks! One thing though: this now creates an inconsistency with Nit: |
Signed-off-by: w3lld1 <[email protected]>
|
Addressed the consistency issue in
Validation:
|
|
Another small nit: since |
|
Agreed — moved the three Validation:
|
Summary
group_membersexpires_atvalues to GitLab'sYYYY-MM-DDstring format before comparing or saving user membershipsgroup_members.groups/ share-with-group expiry valuesFixes #1320
Validation
uv run qa lint ruff gitlabform/processors/group/group_members_processor.py tests/unit/processors/test_group_members_processor.pyuv run qa format --check gitlabform/processors/group/group_members_processor.py tests/unit/processors/test_group_members_processor.pyuv run qa test tests/unit/processors/test_group_members_processor.pyuv run qa test tests/unitI did not run acceptance tests because they require a disposable GitLab instance/Docker setup.