You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ This tool automates the process, allowing you to sync secrets across multiple re
18
18
19
19
## Usage
20
20
21
-
**Create a configuration file** (`secrets.config.yaml`) in your central repository:
21
+
**Create a configuration file** (`secrets.config.yaml`) in your central repository or local directory:
22
22
23
23
```yaml
24
24
repos:
@@ -29,7 +29,8 @@ envs:
29
29
- OVSX_PAT
30
30
```
31
31
32
-
> **Note**: Both `repos` and `envs` support `*` wildcards. For `repos`, the tool lists all repositories accessible by your token and filters by the pattern (e.g., `owner/vscode-*`). For `envs`, wildcards are expanded by listing secrets from the central repository and matching by name. The central repository is auto-detected in GitHub Actions (from the checked-out repo); for local runs, pass `--repo <owner/repo>`.
32
+
> [!NOTE]
33
+
> Both `repos` and `envs` support `*` wildcards. For `repos`, the tool lists all repositories accessible by your token and filters by the pattern (e.g., `owner/vscode-*`). For `envs`, wildcards are expanded by listing secrets from the central repository and matching by name. The central repository is auto-detected in GitHub Actions (from the checked-out repo); for local runs, pass `--repo <owner/repo>`.
33
34
34
35
### Local usage
35
36
@@ -76,7 +77,8 @@ jobs:
76
77
node-version: lts/*
77
78
78
79
- name: Sync Secrets
79
-
run: npx gh-secrets-sync
80
+
# if regex patterns are used in `repos` or `secrets` must set `--yes` in GitHub Actions
0 commit comments