Repository navigation
docs: serve security.txt and point the support page to the bug bounty - #13315
Merged
mergify[bot] merged 1 commit intoOct 8, 2026
Conversation
docs.mergify.com now serves an RFC 9116 `/.well-known/security.txt` whose only contact is the HackerOne program, with `Policy` pointing to the security page's "Vulnerability Disclosure" section. The path is excluded in `_routes.json` so it is served as a static `text/plain` file without going through the Pages middleware. The support page gains a "Report a Security Vulnerability" section that sends researchers to HackerOne instead of the support queue. The `Expires` field (2027-10-01) has to be renewed before that date. Related to MRGFY-10192 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Change-Id: I87f609e7d5d4cf23e76ae8baf7638a5a42397bab
Contributor
Merge Protections🟢 All 5 merge protections satisfied — ready to merge. Show 5 satisfied protections🟢 👀 Review Requirements
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 Reviews
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
jd
approved these changes
Oct 8, 2026
JulianMaurin
marked this pull request as ready for review
October 8, 2026 09:54
Contributor
Merge Queue Status
This pull request spent 2 minutes 59 seconds in the queue, including 2 minutes 38 seconds running CI. Required conditions to merge
|
36 of 49 tasks
mergify
Bot
deleted the
devs/JulianMaurin/MRGFY-10192/serve-security-txt-point-support-page-bug-bounty--87f609e7
branch
October 8, 2026 09:57
This branch was successfully deployed
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
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.
docs.mergify.com now serves an RFC 9116
/.well-known/security.txtwhose only contact is the HackerOne program, with
Policypointing tothe security page's "Vulnerability Disclosure" section. The path is
excluded in
_routes.jsonso it is served as a statictext/plainfilewithout going through the Pages middleware.
The support page gains a "Report a Security Vulnerability" section that
sends researchers to HackerOne instead of the support queue.
The
Expiresfield (2027-10-01) has to be renewed before that date.Related to MRGFY-10192
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com