Skip to content

build: exclude development files from app releases - #3594

Merged
skjnldsv merged 1 commit into
masterfrom
fix/nextcloudignore
Nov 13, 2026
Merged

skjnldsv merged 1 commit into
masterfrom
fix/nextcloudignore

Conversation

@skjnldsv

Copy link
Copy Markdown
Member

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.

I checked it with git ls-files -ci --exclude-from=.nextcloudignore on master, 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-by trailer.

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>
@skjnldsv
skjnldsv merged commit 46019b5 into master Nov 13, 2026
34 checks passed
@skjnldsv
skjnldsv deleted the fix/nextcloudignore branch November 13, 2026 08:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants