Custom skeleton directory deleted after update #1621

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

– – –

I have an issue with the skeleton directory settings (and the integrity check?).

Steps to reproduce

· I've copied core/skeleton to core/skeleton-c as I knew, the original skeleton directory changes after updates (and didn't know a better place at that time)
· I set 'skeletondirectory' => 'core/skeleton-c', in config.php accordingly.
· Create a new test-user and login, everything as expected (only the files I've placed in core/skeleton-c exist).

Actual behavior

· Then, nextcloud update.
· core/skeleton-c doesn't exist anymore.

Expected behavior

A: Don't delete the custom skeleton directory during/after updates // respect the settings in integrity checks.
B: Update documentation to inform about this behavior and give a proposed place for a custom skeleton directory.
C: Do both :)

Server configuration

Added as needed. This issue doesn't seem to depend on most of this at all. Please tell me if I'm wrong.
Operating system: Linux, Arch
File system: ext4
Web server:
Database:
PHP version: 7.4.25
Nextcloud version: 21.0.5 (docker fpm)

Updated from an older Nextcloud/ownCloud or fresh install: From nextcloud 21.0.4 or smth. like that (eg. 21.0.3).

Signing status:

No errors have been found.

Logs

I don't know since when the directory went missing tbh.

– – –

I'm looking forward to your response.

edit.: To clarify: I consider this as a bug because of unwanted/undocumented behavior. However, this may be seen as a feature request as well.