secret version promote --help said promote "Updates the current symlink to point to the specified version". There is no symlink: a secret's current is a plain file holding the version name, and promote rewrites it, which is what the README already says. The help text now says promote rewrites the secret's current file to name the version, and the comment above the SetCurrentVersion call in PromoteVersion says the same.
A new test runs secret version promote --help in process and checks that the output does not contain "symlink" and does contain "current file".
Left alone, outside this issue: comments in internal/cli/integration_test.go still describe a current symlink.
Model: opus-5-5
`secret version promote --help` said promote "Updates the current symlink to point to the specified version". There is no symlink: a secret's `current` is a plain file holding the version name, and promote rewrites it, which is what the README already says. The help text now says promote rewrites the secret's current file to name the version, and the comment above the `SetCurrentVersion` call in `PromoteVersion` says the same.
A new test runs `secret version promote --help` in process and checks that the output does not contain "symlink" and does contain "current file".
Fixes https://git.eeqj.de/sneak/secret/issues/153
Left alone, outside this issue: comments in `internal/cli/integration_test.go` still describe a current symlink.
Model: opus-5-5
The help text for `secret version promote` and a comment in
PromoteVersion said promote updates a "current symlink". `current` is a
plain file holding the version name, and promote rewrites it; the README
already says so. A new test runs `secret version promote --help` and
checks the output does not mention a symlink and does name the current
file.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
secret version promote --helpsaid promote "Updates the current symlink to point to the specified version". There is no symlink: a secret'scurrentis a plain file holding the version name, and promote rewrites it, which is what the README already says. The help text now says promote rewrites the secret's current file to name the version, and the comment above theSetCurrentVersioncall inPromoteVersionsays the same.A new test runs
secret version promote --helpin process and checks that the output does not contain "symlink" and does contain "current file".Fixes #153
Left alone, outside this issue: comments in
internal/cli/integration_test.gostill describe a current symlink.Model: opus-5-5
8b7c2b2a73to0ed413a2a1Review passed.
Model: opus-5-5