Request: enable pull requests for community contributions

[Anazeez]

I prepared a contribution on my fork:
https://github.com/Anazeez/deepseek-harness/tree/feature/offline-local-ai-playground

The branch is verified with static checks, full tests, and host build. GitHub currently reports that pull requests are disabled for this repository. Could an owner enable pull requests, or advise the preferred contribution route?

[PerryLink]

Short version: this is a maintainer decision, and the current answer is written down in the repository.

CONTRIBUTING.md:9 says it directly:

DeepSeek Harness is still at an early stage and under active development. We are sorry that we cannot accept external pull requests at the moment.

So it is a deliberate status, not a missing setting someone forgot to flip. Two things you can verify yourself: the repository has no pull requests at all — querying every pull request in any state returns totalCount: 0 — and the GitLab CI file in the repo (.gitlab-ci.yml:1-4) triggers only on python-v* tags with no merge_request rules, i.e. that pipeline is a Python package release outlet, not a code-review path.

Because your work sits on your own fork (Anazeez/deepseek-harness), there is no route that turns it into a PR right now — a branch on a fork is not visible to this repository until a PR exists, and PRs are not being accepted.

The alternatives CONTRIBUTING.md:11-17 lists as the contribution routes that do work today:

• Report issues or bugs in GitHub Discussions, and upvote the ones you want the team to see. The same paragraph notes the team is small and may not reply to everything, but does read them and weighs them when allocating resources.
• Contribute to the ecosystem: publish a plugin and tag the repository with the dsh-plugin topic, write blog posts or how-to guides, and answer other people's questions.
• README.md:45-47 repeats the same channels: Discussions for feedback and bug reports, the dsh-plugin topic for plugin discoverability, and the Discord community.

Whether pull requests open later is entirely up to the maintainers; nobody outside the team can promise it, and I am not going to guess at a timeline. What is fair to say is that your request is on the record here — this category of post is exactly what the team says it monitors when it allocates work.

If the route list answers your question, marking this as the answer will help the next contributor who lands here after hitting the same disabled-PR page; the PR policy itself stays with the maintainers.