Skip to content

Document requirement to push to private forks - #18

Merged
MartinaeyNL merged 1 commit into
mainfrom
vulnerability-management
Nov 19, 2026
Merged

MartinaeyNL merged 1 commit into
mainfrom
vulnerability-management

Conversation

@Ekhorn

@Ekhorn Ekhorn commented Nov 18, 2026

Copy link
Copy Markdown
Contributor

Being able to see a security advisory and its private fork doesn't give push access. A push fails with Write access to repository not granted (HTTP 403) until you're a collaborator on the advisory.

  • Add a paragraph to "Developing the fix": add yourself or the openremote/security-managers team as a collaborator on the advisory before pushing
  • Quote the error message so it can be found by searching for it

See https://github.com/orgs/community/discussions/195149 for the same problem reported by another project.

@Ekhorn
Ekhorn requested a review from a team November 18, 2026 20:22
@Ekhorn Ekhorn self-assigned this Nov 18, 2026
@MartinaeyNL
MartinaeyNL merged commit 8f04c29 into main Nov 19, 2026
2 checks passed
@MartinaeyNL
MartinaeyNL deleted the vulnerability-management branch November 19, 2026 10:09
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