WordPress / WordPress/Documentation-Issue-Tracker
[Advanced Admin] Document options which drive auto-update behavior.
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 109
- Forks
- 73
- PR merge metrics
- No merged PRs in 30d
Description
Issue Description
Document WordPress options related to auto updates.
URL of the Page with the Issue
https://wordpress.org/documentation/article/configuring-automatic-background-updates/
Section of Page with the issue
New section
Why is this a problem?
How updates function by default don't seem to be documented.
Suggested Fix
The following WordPress options are not documented but seem to be the way that updates are set most of the time:
- auto_update_core_dev: Allows development versions to be updated to only if a development version is already installed.
- auto_update_core_minor: Minor core updates, such as maintenance and security releases
- auto_update_core_major: Major core release updates
Please see also the discussion in slack: https://wordpress.slack.com/archives/CULBN711P/p1675903173889349
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the “Configuring Automatic Background Updates” page at the supplied URL and review the existing content around the proposed new section. Consult the linked Slack discussion for context, then document the three listed WordPress options and their default auto-update behavior. Done means the page explains these options clearly in the new section.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wordpress
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 76/100