[GH-ISSUE #2442] Unable to create PR from fork: "must be a collaborator" #6674

Closed
opened 2026-04-20 17:15:53 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @deadLocks21 on GitHub (Mar 23, 2026).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2442

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same problem.

Description

Unable to create PR from fork: "must be a collaborator"

I'm trying to contribute to Vikunja by opening a pull request from my fork (deadLocks21/vikunja, branch feat/filter-include-nulls-view) to go-vikunja/vikunja:main.

The comparison page shows "Able to merge" and everything looks correct, but when I click "Create pull request", I get:

Pull request creation failed. Validation failed: must be a collaborator

This is likely caused by the new GitHub repository setting introduced in February 2026 ([changelog](https://github.blog/changelog/2026-02-13-new-repository-settings-for-configuring-pull-request-access/)) that restricts pull request creation to collaborators only. This setting can be found under Settings > General > Features.

This is a known issue affecting many open-source projects, see [community discussion #61472](https://github.com/orgs/community/discussions/61472).

Could this setting be disabled to allow contributions from external forks? Happy to re-submit my PR once it's resolved.

My branch: https://github.com/deadLocks21/vikunja/compare/main...feat/filter-include-nulls-view

Vikunja Version

v2.2.0

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Please select

Screenshots

Image
Originally created by @deadLocks21 on GitHub (Mar 23, 2026). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2442 ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description # Unable to create PR from fork: "must be a collaborator" I'm trying to contribute to Vikunja by opening a pull request from my fork (`deadLocks21/vikunja`, branch `feat/filter-include-nulls-view`) to `go-vikunja/vikunja:main`. The comparison page shows "Able to merge" and everything looks correct, but when I click "Create pull request", I get: > Pull request creation failed. Validation failed: must be a collaborator This is likely caused by the new GitHub repository setting introduced in February 2026 ([[changelog](https://github.blog/changelog/2026-02-13-new-repository-settings-for-configuring-pull-request-access/)](https://github.blog/changelog/2026-02-13-new-repository-settings-for-configuring-pull-request-access/)) that restricts pull request creation to collaborators only. This setting can be found under **Settings > General > Features**. This is a known issue affecting many open-source projects, see [[community discussion #61472](https://github.com/orgs/community/discussions/61472)](https://github.com/orgs/community/discussions/61472). Could this setting be disabled to allow contributions from external forks? Happy to re-submit my PR once it's resolved. **My branch:** https://github.com/deadLocks21/vikunja/compare/main...feat/filter-include-nulls-view ### Vikunja Version v2.2.0 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Please select ### Screenshots <img width="1624" height="1061" alt="Image" src="https://github.com/user-attachments/assets/1ac2c36d-1fa8-480d-9fc5-6163f741068b" />
Author
Owner

@deadLocks21 commented on GitHub (Mar 23, 2026):

Issue seems to be resolved, I was able to create my PR.

<!-- gh-comment-id:4110805866 --> @deadLocks21 commented on GitHub (Mar 23, 2026): Issue seems to be resolved, I was able to create my PR.
Author
Owner

@kolaente commented on GitHub (Mar 23, 2026):

Interesting, the setting has not been changed.

<!-- gh-comment-id:4111945109 --> @kolaente commented on GitHub (Mar 23, 2026): Interesting, the setting has not been changed.
Author
Owner

@deadLocks21 commented on GitHub (Mar 23, 2026):

That is indeed surprising... maybe a bug in the GitHub UI?

<!-- gh-comment-id:4112202056 --> @deadLocks21 commented on GitHub (Mar 23, 2026): That is indeed surprising... maybe a bug in the GitHub UI?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#6674