Repository navigation
Conversation
List every development file the release tooling still has to remove, anchored to the app root and sorted, so the app's own .nextcloudignore covers them. composer.json, package.json and their lock files stay in the release for traceability. Assisted-by: ClaudeCode:claude-opus-5-5 Signed-off-by: John Molakvoæ <14975046+skjnldsv@users.noreply.github.com>
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
The release build still has to delete these development files itself because this app's .nextcloudignore doesn't list them. nextcloud-releases/server#137 now reports that per app. This adds them, anchored to the app root and sorted like recommendations' file. composer.json, package.json and their lock files stay in the release on purpose, for traceability.
It also stops removing composer.json and package.json. Existing entries are now anchored to the app root, which doesn't change what ships. It also drops entries for files that no longer exist on any branch. It also ignores dev files found in this repo:
/APPS.md.I checked it with
git ls-files -ci --exclude-from=.nextcloudignoreon main, stable35, stable34 and stable33: no development file is left at the root, and nothing else changes in what ships.👾 This pull request was assisted by Claude Code, commits carry an
Assisted-bytrailer.