-
Notifications
You must be signed in to change notification settings - Fork 84
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
base: main
Are you sure you want to change the base?
Conversation
plus fix a typo
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:
|
@richard67 May you check and merge? |
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:
|
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) |
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 😄 |
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 📝
new-features.md
Add instructions for pre-testing automated updates in 5.4
migrations/53-54/new-features.md
alpha.
new-features.md
Fix typo in batch processing feature title
migrations/54-60/new-features.md