From bc74ff90d63b025b399bac375404cbcb7ae2d94e Mon Sep 17 00:00:00 2001 From: Ekhorn Date: Wed, 18 Nov 2026 21:14:42 +0100 Subject: [PATCH] Document requirement to push to private forks --- docs/vulnerability-management-and-coordinated-disclosure.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/vulnerability-management-and-coordinated-disclosure.md b/docs/vulnerability-management-and-coordinated-disclosure.md index f296084..53e8706 100644 --- a/docs/vulnerability-management-and-coordinated-disclosure.md +++ b/docs/vulnerability-management-and-coordinated-disclosure.md @@ -51,6 +51,8 @@ Although work on the fork can still be performed in a branch, it does not bring Once a PR is created, it will not appear in the normal PR list, it must be accessed via the advisory page. Similarly, it must be merged from the advisory page and by a person from the “openremote/product-owners” team. +Pushing to the fork requires being a collaborator on the advisory. Being able to see the advisory and the fork is not enough, the push fails with `remote: Write access to repository not granted.` Add yourself or the “openremote/security-managers” team as a collaborator on the advisory page first. + Because the fork runs no CI, the pipeline checks have to pass locally before the fix is proposed for merge. ### Merging