Skip to content

Conversation

@joshtrichards
Copy link
Member

☑️ Resolves

  • Reorders the “Patching Nextcloud” chapter to match a user’s workflow: obtain a patch first, then apply it (server/apps), and finally learn how to revert.
  • Moves and clarifies guidance on common patch warnings (build/tests files) under a dedicated “Notes and troubleshooting” section (i.e. applicable to both server+app patches).
  • Tightens language throughout for readability.
  • Fix randomly cut-off sentence in the error Note.

🖼️ Screenshots

BEFORE

image

AFTER

image

- Move “Getting a patch from a GitHub pull request” section before applying steps and rename it to “Obtaining a patch”
- Add “Notes and troubleshooting” section
- Improve grammar, punctuation, and phrasing
- Clarify backport guidance + include actual backport PR/URLs
- Fix randomly cut-off sentence in the error Note

Signed-off-by: Josh <josh.t.richards@gmail.com>
@joshtrichards joshtrichards added this to the Nextcloud 33 milestone Nov 17, 2025
@joshtrichards joshtrichards changed the title docs(admin_manual) reorder “Patching Nextcloud” for logical flow docs(admin_manual): reorder “Patching Nextcloud” for logical flow Nov 17, 2025
Copy link
Member

@ChristophWurst ChristophWurst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice 👏

Thank you very much

@joshtrichards joshtrichards merged commit 98c138e into master Nov 18, 2025
13 checks passed
@joshtrichards joshtrichards deleted the jtr/admin-patching-reorg branch November 18, 2025 12:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants