lelandf

By default, WordPress will not apply <a href="https://codex.wordpress.org/Configuring_Automatic_Background_Updates" rel="nofollow ugc">automatic background updates</a> if it detects a version control system (like Git or Subversion) in the WordPress directory or any of its parent directories.
WordPress does this because it assumes that if version control systems are present, the site owners have their own system in place for managing updates, and WordPress doesn’t want to mess with that.
However, minor updates can contain critical security vulnerability fixes, and those aforementioned site owners may consider the benefit of having minor releases automatically updated by WordPress greater than the risks of waiting too long to apply those updates themselves.
If that sounds like you, then you may wish to consider installing this option-free plugin.
Just activate when you need it.
Perhaps before a “disconnected” vacation when you don’t want to run the risk of a security update being released during it, and having no way of applying said update until your return.
Deactivate it when you don’t.

Forced Auto Updates

Apply automatic background updates for minor releases of WordPress core, even with version control systems present.

WordPress.org

Dion Hulse

Andrew Nacin

Most sites are able to apply updates in the background. Background Update Tester checks your site for compatibility and explains any problems.
After activating this plugin, visit the Dashboard → Update Tester screen. (If you are using multisite, visit Updates → Update Tester in the network admin.)
This is an initial release.

Background Update Tester

Most sites are able to apply updates in the background. Background Update Tester checks your site for compatibility and explains any problems.

Forced Auto Updates vs Background Update Tester