Skip to content

Commit 60552e0

Browse files
committed
docs: record repository cleanup and keep only server config template
1 parent 5d09f1b commit 60552e0

2 files changed

Lines changed: 153 additions & 98 deletions

File tree

config.example.yaml

Lines changed: 0 additions & 98 deletions
This file was deleted.
Lines changed: 153 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,153 @@
1+
# Repository Cleanup Log
2+
3+
## Overview
4+
5+
This document records the repository cleanup work completed in the local repository during the current maintenance session.
6+
7+
The work focused on:
8+
9+
- removing leaked configuration and service-specific references from Git history
10+
- removing `OneDrive` and `SharePoint` related plugin traces
11+
- removing committed binary payload resources from the main repository history
12+
- adding ignore rules for local-only generated artifacts and local community resources
13+
14+
This document is a maintenance record. It does not change the current submodule layout.
15+
16+
## Scope
17+
18+
The cleanup covered the main repository only.
19+
20+
The following were intentionally excluded from cleanup changes:
21+
22+
- `external/IoM-go`
23+
- other `external/` submodules
24+
- the current submodule path definition for the community intl repository
25+
26+
## History Rewrites Performed
27+
28+
The local Git history was rewritten to remove or scrub the following:
29+
30+
- `OneDrive` / `SharePoint` related code and text references
31+
- leaked Azure application secret and associated connection strings
32+
- committed community binary resource directories
33+
34+
The following historical paths were removed from the main repository history:
35+
36+
- `client/command/onedrive`
37+
- `helper/intl/custom/onedrive`
38+
- `helper/intl/community/resources`
39+
- `helper/consts/community/resources`
40+
41+
The following content classes were scrubbed from history:
42+
43+
- `OneDrive`
44+
- `SharePoint`
45+
- Azure application secret values
46+
- connection strings containing the leaked secret
47+
48+
## Current OneDrive Status
49+
50+
Current verification results:
51+
52+
- no `OneDrive` or `SharePoint` matches were found in the current tracked working tree
53+
- no `OneDrive` or `SharePoint` matches were found in local commit messages
54+
- no `OneDrive` or `SharePoint` matches were found in local commit diffs
55+
56+
Searches used during verification included:
57+
58+
- case-insensitive content scan of the repository working tree
59+
- case-insensitive filename and path scan
60+
- `git log --grep` over all local refs
61+
- `git log -G` over all local refs
62+
63+
## Binary Cleanup Status
64+
65+
The main repository history previously contained committed binary payload resources under community resource directories.
66+
67+
These historical directories were removed from the main repository history:
68+
69+
- `helper/intl/community/resources`
70+
- `helper/consts/community/resources`
71+
72+
After the history rewrite, the main repository no longer reports tracked historical blobs with extensions such as:
73+
74+
- `.exe`
75+
- `.dll`
76+
- `.bin`
77+
- `.db`
78+
- `.sqlite`
79+
80+
The following categories were intentionally not treated as repository pollution:
81+
82+
- documentation images under `docs/assets`
83+
- dependency content under `external/`
84+
85+
## Ignore Rules Added
86+
87+
The local `.gitignore` was extended to prevent reintroducing local-only files.
88+
89+
Added ignore coverage includes:
90+
91+
- local config files
92+
- local auth and log files
93+
- local build outputs
94+
- local test executables
95+
- local community resource directories and files
96+
97+
Relevant current ignore entries include:
98+
99+
- `/config.yaml`
100+
- `/server/config.yaml`
101+
- `*.auth`
102+
- `*.log`
103+
- `*.test.exe`
104+
- `/client.exe`
105+
- `/server.exe`
106+
- `/client_linux_amd64`
107+
- `/server_linux_amd64`
108+
- `/core`
109+
- `/testinventory.exe`
110+
- `helper/intl/community/resources/`
111+
- `helper/intl/community/modules/`
112+
- `helper/intl/community/main.lua`
113+
- `helper/intl/community/mal.yaml`
114+
115+
## Local Commits Added
116+
117+
The following local commits were added as part of the cleanup session:
118+
119+
- `394fc2d1` `chore: ignore local community resources and build artifacts`
120+
- `5d09f1bf` `chore: ignore local build outputs`
121+
122+
Earlier local history was also rewritten, so commit hashes before the rewrite should not be treated as stable references.
123+
124+
## Current Known Issues
125+
126+
The submodule path definition for the community intl repository is currently inconsistent with the local initialized working tree layout.
127+
128+
Observed state:
129+
130+
- `.gitmodules` records the submodule path as `helper/intl/community/community`
131+
- the local initialized submodule working tree is rooted at `helper/intl/community`
132+
133+
This inconsistency was detected during the cleanup session but was intentionally left unchanged.
134+
135+
Current working tree items that remain outside the scope of this cleanup:
136+
137+
- modified submodule state in `external/IoM-go`
138+
- unresolved community intl submodule path mismatch
139+
140+
## Verification Summary
141+
142+
Completed verification steps:
143+
144+
1. verified that `OneDrive` / `SharePoint` content no longer appears in the main repository working tree
145+
2. verified that `OneDrive` / `SharePoint` content no longer appears in local Git history searches
146+
3. verified that previously committed community binary resource paths no longer appear in local Git history
147+
4. verified that local ignore rules cover the identified generated artifacts
148+
149+
## Operational Note
150+
151+
Because Git history was rewritten, any remote synchronization must use forced push operations from a network environment that can successfully push to GitHub.
152+
153+
This document records local repository state only. It does not guarantee that the remote repository has already been updated.

0 commit comments

Comments
 (0)