Integrate sync_schema_config_fields fixes into main#8067
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughA new ChangesField Iteration Helper and Migration Updates
🚥 Pre-merge checks | ✅ 4 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
Fixes #8065
Integrate sync_schema_config_fields fixes into main.
This ports the release branch schema config fix into
mainwhile preserving the newer main-branch schema config locking and de-duplication logic.Checklist
self-explanatory (or properly documented)
Testing instructions
ve/bin/python manage.py sync_schema_config_fields --discipline-id <discipline_id>.accessionId,localityId,collectionObjectId, or other{table}Idfields.ve/bin/python manage.py sync_schema_config_fields --discipline-id <discipline_id> --apply.Summary by CodeRabbit