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: AGENTS.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,8 @@ Guidelines for autonomous contributors working on this repository.
15
15
- Whether it’s TypeScript, shell scripts, or build helpers, any newly introduced function or class must include a concise docstring explaining its role. Update existing docstrings when behavior changes.
16
16
17
17
5.**Tests and validation**
18
-
- Run any available automated checks relevant to your change (unit tests, linting, packaging). If something can’t be run in the current environment, clearly state what remains unverified.
18
+
- Always run the test suite and linter before considering a coding task complete. If something can’t be run in the current environment, clearly state what remains unverified.
19
+
- Run any other available automated checks relevant to your change (e.g., packaging). If something can’t be run in the current environment, clearly state what remains unverified.
19
20
20
21
6.**Commit messaging**
21
22
- When suggesting or creating commit titles, always follow the [Conventional Commits](https://www.conventionalcommits.org/) format (e.g., `feat: add highlight toggle command`). Include scope when it adds clarity.
Copy file name to clipboardExpand all lines: README.md
+29Lines changed: 29 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,6 +36,7 @@ See the [Build and install](#build-and-install) section below for how to build a
36
36
-[**View Mode**](#view-mode) - View findings in a list, or grouped by filename.
37
37
-[**Multiple Users**](#multiple-users) - Findings can be viewed from multiple different users.
38
38
-[**Hide Findings**](#hide-findings) - Hide all findings associated with a specific user.
39
+
-[**Auto Sync (Git)**](#auto-sync-git) - Automatically sync .weaudit files across auditors via a dedicated branch.
39
40
-[**Search & Filter Findings**](#search--filter-findings) - Search and filter the findings in the _List of Findings_ panel.
40
41
-[**Export Findings**](#export-findings) - Export findings to a markdown file.
41
42
-[**Drag & drop Findings and Locations**](#drag--drop-findings-and-locations) - Drag and drop findings and locations in the _List of Findings_ panel.
@@ -87,6 +88,7 @@ You can quickly navigate through all partially audited regions in your workspace
87
88
### Detailed Findings
88
89
89
90
You can fill detailed information about a finding by clicking on it in the _List of Findings_ view in the sidebar. The respective _Finding Details_ panel will open, where you can fill the information.
91
+
The panel also shows a read-only provenance field (defaulting to "human") to indicate who created the finding.
@@ -140,6 +142,7 @@ You can share the weAudit file with you co-auditors to share findings. This file
140
142
141
143
In the `weAudit Files` panel, you can toggle to show or hide the findings from each user by clicking on the entries.
142
144
There are color settings for other user's findings and notes, and for your own findings and notes.
145
+
Findings and notes show the author's username after the filename/line number in the _List of Findings_ panel.
143
146
144
147

145
148
@@ -148,6 +151,22 @@ You can hide all findings associated with a specific user by clicking on that us
148
151
149
152

150
153
154
+
### Auto Sync (Git)
155
+
weAudit can automatically sync `.weaudit` files across auditors using a dedicated git branch.
156
+
157
+
To enable, set `weAudit.sync.enabled` to `true` in your settings. By default, weAudit:
158
+
- uses the `weaudit-sync` branch on the `origin` remote;
159
+
- pulls the latest sync branch before committing local `.weaudit` changes;
160
+
- polls every minute for remote updates (configurable);
161
+
- syncs only `.vscode/*.weaudit` files.
162
+
163
+
Sync runs from a dedicated git worktree stored in VS Code's global storage, so your current branch and working tree stay untouched.
164
+
165
+
You can also configure these settings in the **Sync Configuration** panel in the weAudit sidebar.
166
+
The panel shows the timestamp of the last successful sync.
167
+
168
+
You can trigger a manual sync at any time with the `weAudit: Sync Findings Now` command.
169
+
151
170
### Toggle Highlights
152
171
Hide every findings/notes highlight in the editor by running the `weAudit: Toggle Findings Highlighting` command from the Command Palette. Run the command again to bring the highlights back whenever you need to review them.
153
172
@@ -177,6 +196,16 @@ You can drag and drop findings and locations in the _List of Findings_ panel to:
177
196
-`weAudit.general.username`: Username to use as finding's author (defaults to system username if empty)
178
197
-`weAudit.general.permalinkSeparator`: Separator to use in permalinks (\\n is interpreted as newline)
179
198
199
+
#### Sync settings
200
+
201
+
-`weAudit.sync.enabled`: Enable git-based auto sync (opt-in)
202
+
-`weAudit.sync.remoteName`: Git remote to use (default: "origin")
203
+
-`weAudit.sync.branchName`: Sync branch name (default: "weaudit-sync")
204
+
-`weAudit.sync.pollMinutes`: Remote polling interval in minutes (default: 1)
205
+
-`weAudit.sync.debounceMs`: Debounce delay for local changes in milliseconds
206
+
207
+
Sync settings are stored per-workspace (user-level settings are ignored).
208
+
180
209
#### Background colors
181
210
182
211
Each background color is customizable via the VSCode settings page. Write as #RGB, #RGBA, #RRGGBB or #RRGGBBAA:
0 commit comments