PR template branch guidance can block contributors when next branch is unavailable #44183
Description
Feedback
The PR template asks contributors to choose current or next, but next is not always present in active forks/clones.
This can cause confusion during submission and lead to incorrect branch targeting attempts.
Suggested fix: add conditional wording like “use next if it exists for that release cycle, otherwise use the active contribution branch documented by maintainers”.
URL
https://github.com/home-assistant/home-assistant.io/blob/current/.github/PULL_REQUEST_TEMPLATE.md
Version
No response
Additional information
No response