fix(oss_item): preserve copyright statement order - #315
Conversation
set() iteration follows PYTHONHASHSEED, so the same copyright lines were reported in a different order on each run.
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: fosslight/fosslight_util/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthrough
ChangesCopyright order
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Suggested reviewers: Merge Risk: ⚪ Minimal · up to The change makes duplicate copyright normalization retain first-seen order, with tests covering string and list inputs. No concrete merge-blocking risk is identified. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 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 |
set() order follows PYTHONHASHSEED. Sorting the unique lines keeps the report stable at the same cost as the set itself.
Summary
OssItem.copyrightdeduplicated statements withset(), whose iteration order followsPYTHONHASHSEED.README.md) were therefore emitted in a different order on each process, which showed up as a PyPI-install vs git-install difference.