Skip to content

docs(mail): document user-level allow/blocked sender concept#1315

Open
chumbleyneria wants to merge 1 commit into
larksuite:mainfrom
chumbleyneria:feat/3b480f1
Open

docs(mail): document user-level allow/blocked sender concept#1315
chumbleyneria wants to merge 1 commit into
larksuite:mainfrom
chumbleyneria:feat/3b480f1

Conversation

@chumbleyneria

@chumbleyneria chumbleyneria commented Jun 7, 2026

Copy link
Copy Markdown

Generated by the harness-coding skill.

  • Branch: feat/3b480f1
  • Target: main

Sprints

ID Title Status Commit
S7 Regenerate lark-cli artifacts for user allow/block sender commands passed 1e01dd7

This PR was created autonomously. Quality gates were enforced by the repo's own pre-commit hooks.

Summary by CodeRabbit

  • Documentation
    • Documented new user-level sender allow/block list management features, including batch operations, keyword search, and pagination capabilities. Clarified that allow and block lists are mutually exclusive and operate independently from admin-level controls.

Add a 核心概念 entry for the user-level sender allow/blocked lists so the
generated mail SKILL.md surfaces the new user_mailbox.allow_senders /
user_mailbox.blocked_senders capability to AI agents. The command metadata
and scope tables themselves flow into the repo via the registry-produced
meta_data.json that build-time fetch_meta.py pulls (gitignored, not hand
edited); this template concept entry is the only checked-in source touchpoint
for the new resource.

sprint: S7
@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@coderabbitai

coderabbitai Bot commented Jun 7, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 70b6f924-01a7-475a-8e4a-4b7c6138f06d

📥 Commits

Reviewing files that changed from the base of the PR and between e1bb9db and 1e01dd7.

📒 Files selected for processing (1)
  • skill-template/domains/mail.md

📝 Walkthrough

Walkthrough

Documentation added to the mail skill template describing user-level sender allow/block lists, including the two managing resources, mutual exclusivity, supported operations (batch_create, batch_remove, list), and scoping mechanics with me alias and separation from admin/tenant-level sender mechanisms.

Changes

Mail domain user-level sender lists documentation

Layer / File(s) Summary
User-level sender allow/block lists documentation
skill-template/domains/mail.md
Documentation added for 发件人黑白名单 (sender allow/block lists) under 核心概念, covering resources (user_mailbox.allow_senders, user_mailbox.blocked_senders), mutual exclusivity, supported operations (batch_create, batch_remove, list with keyword), user scoping via me, and distinction from admin/tenant-level sender mechanisms.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

  • larksuite/cli#594: Both PRs modify skill-template/domains/mail.md—this PR adds sender allow/block list documentation while the retrieved PR removes a Git conflict marker in the same file.

Suggested labels

documentation, domain/mail

Suggested reviewers

  • chanthuang
  • infeng

Poem

📧 A rabbit hops through mail so fine,
Adding lists that gently align—
Allow and block, a balance true,
Senders managed, sorted through! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The pull request description is missing required sections (Summary, Changes, Test Plan) from the template and lacks proper structure, though it documents that the PR was autonomously generated and quality gates were enforced. Restructure the description to follow the template: add a Summary section (1-3 sentences on motivation/scope), a Changes section listing the main changes, and a Test Plan section documenting verification steps.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The pull request title accurately describes the main change: adding documentation for the user-level allow/blocked sender concept to the mail domain documentation.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions Bot added the size/S Low-risk docs, CI, test, or chore only changes label Jun 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/S Low-risk docs, CI, test, or chore only changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants