[josepmariapujol-unity]

Description

Starting with Unity 6.7, Input System development has moved to an internal Unity repository, and we no longer accept external pull requests. This PR updates the public-facing docs to reflect that.

Changes:

• README.md
  • Added an [!IMPORTANT] notice at the top: development has moved to an internal repository as of Unity 6.7, and this repository only receives backports for critical bugs and high user pain issues.
  • Updated the "Contribution & Feedback" section: it no longer says user contributions are welcome, and it points to CONTRIBUTIONS.md, Unity Discussions and the Unity Bug Reporter.
• CONTRIBUTIONS.md
  • Replaced the old contribution guidelines (UCA, PR requirements) with a notice that external PRs are no longer accepted and will be closed without review.
  • Points users to the Unity Bug Reporter for bugs and Unity Discussions for feedback, questions and feature requests.
• Issue template
  • Replaced the old forum link (forum.unity.com) with Unity Discussions (https://discussions.unity.com/tag/input-system/159343).

Testing status & QA

n/a

Overall Product Risks

Please rate the potential complexity and halo effect from low to high for the reviewers. Note down potential risks to specific Editor branches if any.

• Complexity: 0
• Halo Effect: 0

Comments to reviewers

Please describe any additional information such as what to focus on, or historical info for the reviewers.

Checklist

Before review:

• Changelog entry added.
  • Explains the change in Changed, Fixed, Added sections.
  • For API change contains an example snippet and/or migration example.
  • JIRA ticket linked, example (case %%). If it is a private issue, just add the case ID without a link.
  • Jira port for the next release set as "Resolved".
• Tests added/changed, if applicable.
  • Functional tests Area_CanDoX, Area_CanDoX_EvenIfYIsTheCase, Area_WhenIDoX_AndYHappens_ThisIsTheResult.
  • Performance tests.
  • Integration tests.
• Docs for new/changed API's.
  • Xmldoc cross references are set correctly.
  • Added explanation how the API works.
  • Usage code examples added.
  • The manual is updated, if needed.

During merge:

• Commit message for squash-merge is prefixed with one of the list:
  • NEW: ___.
  • FIX: ___.
  • DOCS: ___.
  • CHANGE: ___.
  • RELEASE: 1.1.0-preview.3.

[u-pr]

💡 Harness Review

The documentation announces maintenance mode, ends external pull requests, and updates feedback channels. I examined all three changed documents, their surrounding guidance, and the referenced license text; no actionable issues stood out.

_{Reviewed commit 5b2cb91}

_{🤖 Helpful? 👍/👎}

[codecov-github-com]

Codecov Report

All modified and coverable lines are covered by tests ✅

@@             Coverage Diff             @@
##           develop    #2501      +/-   ##
===========================================
- Coverage    78.96%   78.96%   -0.01%     
===========================================
  Files          767      767              
  Lines       140949   140949              
===========================================
- Hits        111305   111304       -1     
- Misses       29644    29645       +1     

Flag	Coverage Δ
inputsystem_Windows_6000.0	5.30% <ø> (ø)
inputsystem_Windows_6000.3	5.30% <ø> (ø)
inputsystem_Windows_6000.6	5.29% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

ℹ️ Need help interpreting these results?