docs:hooks (recover #1636)#1876
Conversation
Introduced documentation guidelines and discovery rules for WordPress hooks in the project. Added initial hook list in docs/hooks/HOOKLIST.MD, and started documenting several action and filter hooks in docs/hooks/actions.md and docs/hooks/filters.md. Updated .gitignore to ignore 'cursor' instead of '.cursor'. Created supporting documentation files and rules for consistent hook documentation.
Updated HOOKLIST.MD to enumerate and mark all action and filter hooks as documented. Added detailed documentation for all action and filter hooks in actions.md and filters.md, including parameters, return values, categories, and descriptions. Also updated .gitignore to ignore .cursor instead of cursor.
# Conflicts: # .gitignore
|
Warning Review limit reached
More reviews will be available in 16 minutes and 4 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ 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 |
2 participants
Recovered from #1636 (originally by @sapayth), rebased onto
developwith merge conflicts resolved. Functionality preserved.Supersedes #1636.