eSlider/go-onlyoffice
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 3 Wiki Activity

chore: keep the re-landed feature files showroom-safe
Release Please / Release Please (push) Skipped
Release / GoReleaser (push) Skipped
Tests / Secret scan (gitleaks) (push) Skipped
Tests / Test (Go 1.25) (push) Skipped
Tests / Test (Go stable) (push) Skipped
Tests / Secret scan (gitleaks) (pull_request) Successful in 4s
Details
Tests / Test (Go stable) (pull_request) Successful in 1m21s
Details
Tests / Test (Go 1.25) (pull_request) Successful in 1m27s
Details

Browse Source 
The conversion / link / sheet commits predate the tree cleanup, so their
comments and README/test examples still carried internal refs. Re-apply
the genericization (no internal hosts, personal names or client file ids).
This commit is contained in:
eSlider
2026-09-22 22:41:58 +01:00
parent 5e73f6c335
commit ff46aad615
10 changed files with 53 additions and 50 deletions
Download Patch File Download Diff File Expand all files Collapse all files
cmd/oo/projects_files.go
+2 -3
View File
@@ -159,9 +159,8 @@ func prjFilesReplaceInCmd() *cobra.Command {
delete is permanent) and uploads the local file fresh. Unlike 'update' this
leaves a single clean version.
Why it exists: on the arc-1 portal, repeated 'update' of a shared document
(the apartment "Info" cover and the Edelweiss contract) accumulated a visible
version history and a stale id. replace-in yields one clean revision; then
Why it exists: repeated 'update' of a shared document accumulated a visible
version history and left a stale id. replace-in yields one clean revision; then
point links at the returned id (or keep an nginx alias for the legacy fileid).
Note: file ids are server-assigned; a fresh upload gets a new id.`,