Skip to content

migrations/5.4 Automated Update hint #478

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

muhme
Copy link
Contributor

@muhme muhme commented May 31, 2025

User description

plus fix a typo


PR Type

documentation


Description

  • Added instructions for pre-testing automated updates in 5.4.

  • Fixed a typo in the batch processing feature title for 5.4-6.0.


Changes walkthrough 📝

Relevant files
Documentation
new-features.md
Add instructions for pre-testing automated updates in 5.4

migrations/53-54/new-features.md

  • Added section on pre-testing automated updates with Joomla 5.4.0
    alpha.
  • Provided plugin link and usage instructions.
  • Included caution about using alpha releases in production.
  • +9/-0     
    new-features.md
    Fix typo in batch processing feature title                             

    migrations/54-60/new-features.md

  • Corrected typo in batch processing feature title.
  • Changed "Remove a Tag From" to "Remove a Tag".
  • +1/-1     

    Need help?
  • Type /help how to ... in the comments thread for any questions about Qodo Merge usage.
  • Check out the documentation for more information.
  • Copy link
    Contributor

    Qodo Merge was enabled for this repository. To continue using it, please link your Git account with your Qodo account here.

    PR Reviewer Guide 🔍

    Here are some key observations to aid the review process:

    ⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
    🧪 No relevant tests
    🔒 No security concerns identified
    ⚡ Recommended focus areas for review

    Typo

    There's a typo in the word "Jommla" which should be "Joomla" in the automated update testing instructions.

    You can pre-test an automated update with Jommla 5.4.0 alpha versions by installing the
    '[System - Alpha Update Server](https://github.com/joomla/joomla-cms/issues/45540)' plugin.

    @muhme
    Copy link
    Contributor Author

    muhme commented May 31, 2025

    @richard67 May you check and merge?

    Copy link
    Contributor

    qodo-merge-pro bot commented May 31, 2025

    Qodo Merge was enabled for this repository. To continue using it, please link your Git account with your Qodo account here.

    PR Code Suggestions ✨

    Explore these optional code suggestions:

    CategorySuggestion                                                                                                                                    Impact
    General
    Fix typo in product name
    Suggestion Impact:The commit implemented the exact suggestion by correcting the typo from 'Jommla' to 'Joomla' in the documentation

    code diff:

    -You can pre-test an automated update with Jommla 5.4.0 alpha versions by installing the
    +You can pre-test an automated update with Joomla 5.4.0 alpha versions by installing the

    There's a typo in the word "Joomla". The correct spelling is "Joomla" not
    "Jommla". This typo could confuse users trying to follow the documentation.

    migrations/53-54/new-features.md [24]

    -You can pre-test an automated update with Jommla 5.4.0 alpha versions by installing the
    +You can pre-test an automated update with Joomla 5.4.0 alpha versions by installing the

    [Suggestion processed]

    Suggestion importance[1-10]: 4

    __

    Why: The suggestion correctly identifies a typo where Jommla should be Joomla. This is a straightforward spelling correction that improves documentation quality and prevents user confusion.

    Low
    • Update

    @HLeithner
    Copy link
    Member

    The manual is a longterm documentation and should not have temporary bug testing instructions, exceptions might be documented issue for old version which is already fixed in newer versions.

    The goal behind this is to reduce maintainace work on the documentation. (Removing outdated parts again)

    @muhme
    Copy link
    Contributor Author

    muhme commented May 31, 2025

    The manual is a longterm documentation

    I generally agree. And for me this is a special case, I also want to get users to test the important auto-update feature even if they are not in the Mattermost/GitHub/JCM bubble. And please trust me, if I'm still alive, I'll keep the 5.4 migration documentation up to date 😄

    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.

    2 participants