[5.4] Docs: Add a PR targeting section to the README

[LadySolveig]

Issue # .

Summary of Changes

Adding a clear guidance to the README.md for contributors on which branch to target when submitting pull requests.
The new section uses a simple classification table to help contributors choose the correct branch based on the type of change.

Testing Instructions

Actual result BEFORE applying this Pull Request

Expected result AFTER applying this Pull Request

Link to documentations

Please select:

• Documentation link for docs.joomla.org:

• No documentation changes for docs.joomla.org needed

• Pull Request link for manual.joomla.org:

• No documentation changes for manual.joomla.org needed

[brianteeman]

Shouldn't the same change also be made in readme.txt?

[LadySolveig]

Good question, they are definitely not the same texts, the txt seems to have a few more passages and probably hasn't been updated for a while.

No, sorry, I was wrong, in the 6 branch it is also written on 6 so it is current.

[LadySolveig]

The How to get a working installation from the source section is also not in the txt-file.
I don't think it's the idea that they are identical, but I can't say for sure. I think that since it is primarily intended to make collaboration here on Github easier and transparent, the .md file is definitely not wrong.

[chmst]

I have tested this item ✅ successfully on 863fcda

Good Idea.

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/46471.}

[dautrich]

I have tested this item ✅ successfully on 863fcda

I agree with Christiane.

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/46471.}

[richard67]

RTC

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/46471.}

[muhme]

✅ Final check before merging with Codespace – to check the formatting. As discussed, the new section ‘Which branch should my pull request target?’ is not included in ‘readme.txt’ and therefore not in the complete/updated package. It is only visible on GitHub or with git clone. I agree that this is OK, as its primary purpose is to make collaboration on GitHub easier.

[muhme]

Thank you @LadySolveig for your contribution. Thank you @brianteeman for commenting. Thank you @chmst and @dautrich for testing.