Repository navigation
Add fork maintainer community baseline and support policy - #34
Conversation
Ship privacy-aware Issues/Discussions guidance, intended-use disclaimer, and contribution docs so the public fork has clear channels without a cold-PR queue.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (9)
🚧 Files skipped from review as they are similar to previous changes (9)
📝 WalkthroughWalkthroughThe pull request establishes MyPySkinDose’s fork identity and maintainer metadata, adds governance, contribution, support, security, and conduct documentation, introduces structured GitHub intake templates, updates project guidance, and pins the PyPI publishing action to an immutable commit. ChangesProject stewardship
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
|
Note Unit test generation is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it. Generating unit tests... This may take up to 20 minutes. |
|
Request timed out after 900000ms (requestId=c2bf52dc-106b-45f2-b036-3a0accb0d055) |
|
@coderabbitai review |
✅ Action performedReview finished.
|
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/ISSUE_TEMPLATE/bug_report.yml:
- Around line 20-27: Update the required no-phi checkbox option in the “Privacy
confirmation” block to include identified screenshots, private URLs, and full
unredacted logs alongside the existing PHI/PII, clinical RDSR, credential, and
institutional identifier prohibitions. Keep the checkbox required and mirror the
complete warning list.
In `@GOVERNANCE.md`:
- Around line 32-34: Update the maintainer-transition checklist in GOVERNANCE.md
to also require synchronizing CONTRIBUTING.md and SECURITY.md, alongside the
existing files and pyproject.toml maintainer metadata.
In `@README.md`:
- Line 315: Update the Bugs and features GitHub Issues description in README.md
to state that the templates require a no-PHI/PII confirmation, and add a
direction for users to consult the privacy policy; do not claim the templates
enforce privacy.
In `@SUPPORT.md`:
- Around line 26-30: Define one concrete supported private intake channel for
privacy and conduct incidents, document it in SUPPORT.md, and use the identical
channel consistently in SECURITY.md and CODE_OF_CONDUCT.md. Update SUPPORT.md
lines 26-30 to name the channel, SECURITY.md lines 30-34 to replace “contact the
maintainer privately,” and CODE_OF_CONDUCT.md lines 61-65 to replace private
GitHub contact wording.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 5ae68829-ca65-4b7f-aeb2-e7e4161227b3
⛔ Files ignored due to path filters (5)
dev-docs/FORK_MAINTAINER_GUIDE.mdis excluded by!dev-docs/**dev-docs/MYPYSKINDOSE_MIGRATION_STATUS.mdis excluded by!dev-docs/**dev-docs/THIRD_PARTY_NOTICES.mdis excluded by!dev-docs/**dev-docs/TO_DO.mdis excluded by!dev-docs/**dev-docs/index.mdis excluded by!dev-docs/**
📒 Files selected for processing (15)
.github/ISSUE_TEMPLATE/bug_report.yml.github/ISSUE_TEMPLATE/config.yml.github/ISSUE_TEMPLATE/feature_request.yml.github/pull_request_template.md.github/workflows/release.ymlAGENTS.mdCHANGELOG.mdCITATION.cffCODE_OF_CONDUCT.mdCONTRIBUTING.mdGOVERNANCE.mdREADME.mdSECURITY.mdSUPPORT.mdpyproject.toml
Align issue-template privacy checkboxes, clarify Issues wording, expand maintainer-transition checklist, and use private vulnerability reporting as the shared private intake for security, privacy, and CoC reports.
|
@coderabbitai review |
✅ Action performedReview finished.
|
Summary
Test plan
Made with Cursor
Summary by CodeRabbit
Documentation
Community
Release & Maintenance