feat(ci): notify QQ group of Release, Deployment, and Discussion changes

[openai0229]

Chat2DB Edition

Chat2DB Community

Task Category

Contributor infrastructure

Problem

The QQ notification workflow currently covers Issue and pull-request lifecycle changes but omits Release, Deployment, deployment-status, and Discussion lifecycle events. Maintainers cannot see these repository state changes in the existing QQ operations channel.

Scope

• Subscribe the QQ notification workflow to Release lifecycle events.
• Subscribe to Deployment creation and deployment-status changes.
• Subscribe to Discussion lifecycle changes.
• Format bounded Chinese notifications with the event-specific title, state, actor, environment, tag, category, and safe URL when available.
• Add focused tests and update the operations documentation.

Non-goals

• Do not notify on Discussion comments.
• Do not add Issue or pull-request comment/review notifications.
• Do not change the relay authentication, fixed QQ group, or deployment topology.
• Do not send release bodies, discussion bodies, deployment payload data, or credentials.

Completion Criteria

• Release created, published, unpublished, edited, deleted, prereleased, and released actions produce bounded notifications.
• Deployment creation and deployment-status state changes produce bounded notifications.
• Discussion created, edited, deleted, transferred, pinned, unpinned, labeled, unlabeled, locked, unlocked, category-changed, answered, and unanswered actions produce bounded notifications.
• Existing Issue, pull-request, and manual test notifications remain compatible.
• Automated tests cover at least one representative event from each new category.
• A real GitHub Actions event reaches QQ after merge.

Verification

• python3 script/github/test_notify_qq.py
• python3 script/github/qq_relay/test_relay_server.py
• actionlint .github/workflows/ci.yml .github/workflows/qq-group-notifications.yml
• Trigger representative repository events and confirm GitHub Actions plus NapCat logs report successful QQ delivery.

Contribution

I can submit a pull request

Submission Checklist

• I searched existing Issues and Discussions for duplicates.
• I selected the affected Chat2DB edition.
• This proposal does not include credentials, private data, or unpublished vulnerability details.

[github-actions]

Thanks for the clearly bounded contributor-infrastructure proposal. The request is to extend the existing QQ workflow to cover Release, Deployment/deployment-status, and Discussion lifecycle events while keeping notifications bounded and excluding sensitive or body/payload content.

All required maintainer-task fields are present. The next maintainer step is to review the proposed event/action coverage and verification plan; your stated contribution path is a pull request with focused tests and operations-documentation updates.

Generated by AI Issue Assistant for #2003 · 2.78 AIC · ⌖ 2.02 AIC · ⊞ 17.1K · ◷