docs: add donation readiness checklist before enabling donations#46
Merged
MrImmortal09 merged 2 commits intoApr 12, 2026
Merged
Conversation
|
@Abhishek-Dige is attempting to deploy a commit to the mrimmortal09's projects Team on Vercel. A member of the Team first needs to authorize it. |
2 tasks
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
WalkthroughAdded Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (1)
docs/giving-readiness.md (1)
365-369: Use unambiguous date format in revision metadata.
12-04-2026is ambiguous (DD-MM vs MM-DD). Prefer ISOYYYY-MM-DD.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/giving-readiness.md` around lines 365 - 369, Replace the ambiguous date string "12-04-2026" with the ISO format "2026-04-12" in the document; update both occurrences shown in the diff (the revision table entry containing "12-04-2026" and the "**Last Updated**: 12-04-2026" line) so the metadata uses unambiguous YYYY-MM-DD formatting.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/giving-readiness.md`:
- Around line 53-55: The document's "80G Application Process" section references
the obsolete "Form 10G"; update the text to reference the current forms "Form
10A/10AB" (replace any occurrences of "Form 10G" with "Form 10A/10AB" in the
"80G Application Process" checklist and related lines), adjust any accompanying
instructions or bullet points to match the 10A/10AB workflow and required
documents, and apply the same replacement/fix to the other affected ranges
mentioned (lines ~62-65) so the guidance points to the current official forms
and sources.
- Around line 157-160: Update the "Donor Privacy Policy" bullet to be
jurisdiction-aware: change the second sub-bullet to prioritize India (reference
DPDP Act/ Digital Personal Data Protection Act, 2023) and add a conditional note
that GDPR applies only "where EU data subjects are targeted"; keep remaining
bullets about storage/use and opt-in/opt-out intact so the section header "Donor
Privacy Policy" and its other bullets remain unchanged.
- Around line 348-352: The checklist's minimum launch gate currently allows
"/giving" to go live when "80G registration obtained (or application in process
with clear timeline)" — tighten this by requiring actual 80G approval for the
minimum gate: update the checklist item text to read "80G registration obtained"
(remove the "or application in process..." clause), update any related guidance
or conditional language that references the minimum launch requirement for the
/giving page, and ensure any downstream messaging or acceptance criteria that
checks the "80G" state uses the concrete "80G registration obtained" value
(search for the exact string "80G registration obtained (or application in
process with clear timeline)" and replace accordingly).
---
Nitpick comments:
In `@docs/giving-readiness.md`:
- Around line 365-369: Replace the ambiguous date string "12-04-2026" with the
ISO format "2026-04-12" in the document; update both occurrences shown in the
diff (the revision table entry containing "12-04-2026" and the "**Last
Updated**: 12-04-2026" line) so the metadata uses unambiguous YYYY-MM-DD
formatting.
🪄 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: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 33d65027-f853-42ff-a8ba-5a271c0aa6d0
📒 Files selected for processing (1)
docs/giving-readiness.md
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Documents the legal, financial, and operational requirements that must be fulfilled before IIITL / Axios can accept donations through the
/givingpage. This includes banking setup, 80G tax registration, audit trails, governance policies, technical infrastructure, and donor communication processes.No code changes are included in this PR. The
/givingpage remains as "Coming soon" placeholder until all critical requirements are met.Closes #23
Type of Change
Checklist
feat/,fix/,docs/, etc.)pnpm lintand there are no errorspnpm dev)Documentation Overview
The new
docs/giving-readiness.mdcovers:Critical Requirements (Must Complete Before Launch)
Complete Coverage Areas
Next Steps
The issue will remain open as a tracker. Progress can be tracked by checking off items in the markdown document as they are completed.
Screenshots / Screen Recording
Summary by CodeRabbit