Skip to content

Conversation

@luiz1361
Copy link
Contributor

@luiz1361 luiz1361 commented Jan 27, 2026

  • Removed honeycomb-deployment-marker.yml, print-environment.yml, and slack-deployment-message.yml as they are no longer in use.
  • Updated SECURITY.md to clarify the policy regarding security testing and vulnerability disclosure.

Summary by CodeRabbit

  • Chores

    • Removed CI workflows that automated deployment markers, Slack deployment notifications, and printing environment/context during workflow runs.
  • Documentation

    • Updated security policy to restrict unauthorized testing, add an explicit vulnerability disclosure channel, and note no monetary compensation.
    • Removed outdated GitHub organization documentation sections from the README.

✏️ Tip: You can customize this high-level summary in your review settings.

@luiz1361 luiz1361 requested a review from Nova-ZA January 27, 2026 09:29
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 27, 2026

Walkthrough

Removed three GitHub Actions workflows under .github/workflows, removed a README section about org-level GitHub resources, and updated SECURITY.md to require prior authorization for security testing and added a vulnerability disclosure contact and policy notes.

Changes

Cohort / File(s) Summary
Removed CI Workflows
.github/workflows/honeycomb-deployment-marker.yml, .github/workflows/print-environment.yml, .github/workflows/slack-deployment-message.yml
Deleted workflows that: created Honeycomb deploy markers using Vercel data; printed GitHub context/environment; and constructed/sent Slack deployment notifications (included optional Vercel integration and production-branch logic).
Docs / Security
README.md, SECURITY.md
README.md: removed .github org-resources section. SECURITY.md: replaced prior contact guidance with a policy disallowing unauthorized testing, added disclosure email security@prisma.io, noted no monetary compensation, and added related policy notes.

Suggested reviewers

  • Nova-ZA
  • rtbenfield
🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main changes: removal of three unused workflow files and updates to the security policy.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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


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

@luiz1361 luiz1361 self-assigned this Jan 27, 2026
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@SECURITY.md`:
- Around line 3-5: Replace bare links in SECURITY.md: change the plain email
"security@prisma.io" to a mailto link with link text (e.g., [Report a
vulnerability](mailto:security@prisma.io)) and replace the bare URL
"https://trust.prisma.io/" with descriptive link text (e.g., [Prisma Trust
Center](https://trust.prisma.io/)) so both the email and the trust URL use
explicit Markdown link text and satisfy markdownlint MD034.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@SECURITY.md`:
- Line 3: The long single sentence on line 3 should be split into multiple
sentences for clarity: separate the authorization requirement, the disclosure
instruction (include the security@prisma.io email), and the compensation policy
into distinct sentences; update the paragraph that currently reads "To keep our
customer data..." so it becomes three concise sentences covering (1) no security
testing without prior authorization, (2) how to report vulnerabilities via the
specified email address, and (3) that no monetary compensation is offered.

@luiz1361 luiz1361 force-pushed the lm-remove-unused-actions-and-update-security-policy branch from 5ccc797 to be3059b Compare January 27, 2026 09:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants