cadline_web/www_archline_hu
11
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: remove developer backup cruft from the source tree #9

Merged
imre merged 1 commits from chore/remove-dev-cruft into main 2026-07-23 07:25:33 +02:00
Conversation 0 Commits 1 Files Changed 7 -2303
imre.agent commented 2026-07-22 10:58:18 +02:00
Owner
Copy Link

Why

Editor/developer backup copies (*.old, *.orig, *.new) were committed into the source tree. They are dead weight in the deploy source-of-truth and, more importantly, they are old PHP snapshots that a scanner flags as residual/suspicious files. Removing them at the source is the clean fix — better than filtering them out at build time, which would only paper over the fact that they are tracked.

What

git rm of 7 backup files:

  • cadline/backend/maintenance2/maintenance/tips.php.orig
  • cadline/backend/maintenance2/tips.php.orig
  • cadline/components/components/com_showroom/models/uploadgroup.php.old
  • cadline/components/components/com_showroom/views/uploadgroup/tmpl/default.php.old
  • cadline/components/components/com_showroom/views/uploadgroup/view.html.php.old
  • deployed/jckman/administrator/components/com_jckman/restorers/backup.php.old
  • deployed/jckman/administrator/components/com_jckman/views/toolbar/view.html.php.new

None of these are referenced by the running application (the live filenames without the suffix remain in place and untouched).

## Why Editor/developer backup copies (`*.old`, `*.orig`, `*.new`) were committed into the source tree. They are dead weight in the deploy source-of-truth and, more importantly, they are old PHP snapshots that a scanner flags as residual/suspicious files. Removing them at the source is the clean fix — better than filtering them out at build time, which would only paper over the fact that they are tracked. ## What `git rm` of 7 backup files: - `cadline/backend/maintenance2/maintenance/tips.php.orig` - `cadline/backend/maintenance2/tips.php.orig` - `cadline/components/components/com_showroom/models/uploadgroup.php.old` - `cadline/components/components/com_showroom/views/uploadgroup/tmpl/default.php.old` - `cadline/components/components/com_showroom/views/uploadgroup/view.html.php.old` - `deployed/jckman/administrator/components/com_jckman/restorers/backup.php.old` - `deployed/jckman/administrator/components/com_jckman/views/toolbar/view.html.php.new` None of these are referenced by the running application (the live filenames without the suffix remain in place and untouched).
imre.agent added 1 commit 2026-07-22 10:58:19 +02:00 
Stray .old/.orig/.new developer backups (com_showroom uploadgroup,
jckman restorers/toolbar, maintenance2 tips.php) do not belong in a
clean baseline source — they are not deployed code and would only add
noise to the baseline. Remove them at the source rather than filtering
them in build-baseline.sh (the source is the right place to fix this).

The cadline/backend/maintenance SUBMODULE (maintenance.git) also holds
a tips.php.orig — that must be removed in the submodule repo separately.

Ref: cadline/infra#180
imre merged commit 4af8e06eff into main 2026-07-23 07:25:33 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cadline_web/www_archline_hu#9
No description provided.
Delete Branch "chore/remove-dev-cruft"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?