@davmash/bygone 0.8.0 → 0.8.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +20 -0
- package/README.md +9 -1
- package/bin/bygone.js +10 -3
- package/cli/commandSpec.js +9 -0
- package/cli/workingDirectory.js +19 -0
- package/completions/_bygone +1 -0
- package/completions/bygone +1 -1
- package/completions/bygone.fish +1 -0
- package/docs/generating-change-tours.md +8 -0
- package/media/diff.worker.js +5 -0
- package/media/webview.css +1 -1
- package/media/webview.js +250 -188
- package/out/changeTour.js +37 -22
- package/out/standalone-main.js +142 -25
- package/out/tourCoverage.js +37 -22
- package/package.json +2 -1
- package/skills/pr-tour-guide/SKILL.md +238 -0
- package/standalone/index.html +7 -7
- package/web/index.html +9 -9
- package/web/web-host.js +5 -5
|
@@ -0,0 +1,238 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: pr-tour-guide
|
|
3
|
+
description: Act as a PR Tour Guide by generating, validating, compiling, and presenting evidence-grounded Bygone code-change tours from Git ranges. Use for requests such as "Tour this commit for me," or whenever an AI coding agent should explain a pull request, branch, commit, or code change as a guided walkthrough; create or repair a .bygone file; produce an LLM-ready Bygone change context; connect narrative claims to exact source evidence; or turn a diff into a browser-presentable review or demo. Always print the exact `bygone` CLI command to open the resulting diff, review, tour, or history view.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# PR Tour Guide
|
|
7
|
+
|
|
8
|
+
Use Bygone as the deterministic evidence and rendering layer. Treat the language model as the narrative planner, never as the authority on Git ranges or source locations.
|
|
9
|
+
|
|
10
|
+
## Install this skill
|
|
11
|
+
|
|
12
|
+
For Cursor, Codex, Claude Code, and other agents supported by the skills CLI:
|
|
13
|
+
|
|
14
|
+
```sh
|
|
15
|
+
npx skills add davidmashburn/bygone -s pr-tour-guide -g -y
|
|
16
|
+
```
|
|
17
|
+
|
|
18
|
+
List without installing:
|
|
19
|
+
|
|
20
|
+
```sh
|
|
21
|
+
npx skills add davidmashburn/bygone --list
|
|
22
|
+
```
|
|
23
|
+
|
|
24
|
+
From a Bygone source checkout, install the local copy instead:
|
|
25
|
+
|
|
26
|
+
```sh
|
|
27
|
+
npx skills add ./skills/pr-tour-guide -g -y
|
|
28
|
+
```
|
|
29
|
+
|
|
30
|
+
## Install Bygone
|
|
31
|
+
|
|
32
|
+
This skill requires the `bygone` CLI with `tour context`, `tour schema`, `tour validate`, and `tour compile`. Install only when the user asks or when the task cannot proceed without it.
|
|
33
|
+
|
|
34
|
+
**macOS (desktop app + CLI, recommended):**
|
|
35
|
+
|
|
36
|
+
```sh
|
|
37
|
+
brew tap davidmashburn/bygone
|
|
38
|
+
brew install --cask bygone-desktop
|
|
39
|
+
```
|
|
40
|
+
|
|
41
|
+
First install may require `brew trust davidmashburn/bygone`.
|
|
42
|
+
|
|
43
|
+
**CLI only (Node.js required):**
|
|
44
|
+
|
|
45
|
+
```sh
|
|
46
|
+
npm install -g @davmash/bygone
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
**macOS without Homebrew:** download the DMG from [GitHub Releases](https://github.com/davidmashburn/bygone/releases), then choose **Help → Install Command Line Tools…** in the app.
|
|
50
|
+
|
|
51
|
+
**From a Bygone source checkout:**
|
|
52
|
+
|
|
53
|
+
```sh
|
|
54
|
+
npm install
|
|
55
|
+
npm run dev:sync
|
|
56
|
+
```
|
|
57
|
+
|
|
58
|
+
## Locate and verify Bygone
|
|
59
|
+
|
|
60
|
+
Run `bygone --help`. In a Bygone source checkout whose installed command is stale, use `node ./bin/bygone.js` instead.
|
|
61
|
+
|
|
62
|
+
Verify tour support before authoring:
|
|
63
|
+
|
|
64
|
+
```sh
|
|
65
|
+
bygone tour schema >/dev/null
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
If neither `bygone` nor `node ./bin/bygone.js` exposes the `tour` subcommands, stop, share the install commands above, and report that the toolchain is unavailable rather than guessing.
|
|
69
|
+
|
|
70
|
+
Do not rebuild, commit, push, publish, or open a browser unless the user requests it or the surrounding task clearly requires it.
|
|
71
|
+
|
|
72
|
+
## Build the evidence context
|
|
73
|
+
|
|
74
|
+
Determine the intended head and base from the request and repository state. Prefer an explicit base; do not guess when different bases would materially change the explanation.
|
|
75
|
+
|
|
76
|
+
For a hosted review, resolve both immutable endpoint OIDs from provider metadata. Never assume the current checkout is the requested review head. For GitHub:
|
|
77
|
+
|
|
78
|
+
```sh
|
|
79
|
+
PR_JSON="$(gh pr view <n> --json baseRefOid,headRefOid)"
|
|
80
|
+
BASE_OID="$(jq -r .baseRefOid <<<"$PR_JSON")"
|
|
81
|
+
HEAD_OID="$(jq -r .headRefOid <<<"$PR_JSON")"
|
|
82
|
+
test -n "$BASE_OID" && test "$BASE_OID" != null
|
|
83
|
+
test -n "$HEAD_OID" && test "$HEAD_OID" != null
|
|
84
|
+
bygone tour context "$HEAD_OID" --base "$BASE_OID" --output /tmp/change-context.json
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
Use the equivalent API or CLI fields for other providers. If you are not reviewing a hosted change, compute the merge-base against the intended integration branch and pass that exact base OID or ref. Keep the existing preference for explicit endpoints and do not guess.
|
|
88
|
+
|
|
89
|
+
Use immutable commit IDs in the eventual tour. Dirty working-tree changes are reported but excluded from committed-range context.
|
|
90
|
+
|
|
91
|
+
Inspect progressively instead of loading every patch immediately:
|
|
92
|
+
|
|
93
|
+
```sh
|
|
94
|
+
jq '{range,summary,commits,files:[.files[]|{path,previousPath,changeKind,role,additions,deletions,binary,patchOmittedReason,symbolHints}]}' /tmp/change-context.json
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
Then read patches only for likely narrative-bearing files. Account explicitly for every `patchOmittedReason`; never claim to understand omitted binary or oversized evidence.
|
|
98
|
+
|
|
99
|
+
Compiled tours and context dossiers are large because they embed source snapshots. Inspect them progressively and do not load every patch unless the narrative really needs it.
|
|
100
|
+
|
|
101
|
+
## Plan the explanation
|
|
102
|
+
|
|
103
|
+
Identify the smallest set of reviewer questions that makes the change understandable. Organize by conceptual dependency rather than filename order. Usually move through:
|
|
104
|
+
|
|
105
|
+
1. motivation, contract, or invariant;
|
|
106
|
+
2. core implementation;
|
|
107
|
+
3. integration or side effects;
|
|
108
|
+
4. failure behavior and proof.
|
|
109
|
+
|
|
110
|
+
Keep secondary, generated, dependency, and mechanical files in Bygone's complete Files rail unless they alter a reviewer conclusion.
|
|
111
|
+
|
|
112
|
+
Let the change determine the hierarchy. A chapter is a named conceptual arc containing one or more related scenes; a scene answers one reviewer question or advances one thesis. Do not target a fixed chapter count, and do not create a chapter merely to wrap each scene. Repeated one-scene chapters usually indicate that headings are being generated from a template instead of the change's actual structure.
|
|
113
|
+
|
|
114
|
+
Scale the structure proportionally:
|
|
115
|
+
|
|
116
|
+
- A small commit may need one chapter and one scene.
|
|
117
|
+
- A normal pull request often needs one to three chapters with one or more scenes in each.
|
|
118
|
+
- A broad release or long-lived branch may need several chapters, but each boundary must mark a real conceptual transition.
|
|
119
|
+
- Prefer merging adjacent chapters when their scenes form one argument; split a chapter only when its scenes answer materially different reviewer questions.
|
|
120
|
+
|
|
121
|
+
These are pacing heuristics, not quotas. Preserve asymmetry when one capability deserves substantially more explanation than another.
|
|
122
|
+
|
|
123
|
+
Use these narrative constraints:
|
|
124
|
+
|
|
125
|
+
- State one reviewer question or thesis per scene.
|
|
126
|
+
- Give every chapter a coherent multi-scene arc when the material supports one; allow a single-scene chapter only when that scene is independently substantial.
|
|
127
|
+
- Decompose scenes by conceptual need, not a fixed template; do not force every scene to use the same step count.
|
|
128
|
+
- Prefer three to seven steps per scene.
|
|
129
|
+
- Explain why focused code matters instead of paraphrasing syntax.
|
|
130
|
+
- Keep summaries, bullets, annotations, and takeaways distinct; bullets that merely restate the summary are a defect.
|
|
131
|
+
- Avoid intent, safety, performance, or runtime claims unsupported by the evidence.
|
|
132
|
+
- Do not imply that the authored tour exhaustively reviews every changed file.
|
|
133
|
+
|
|
134
|
+
## Author the source
|
|
135
|
+
|
|
136
|
+
Retrieve the current contract:
|
|
137
|
+
|
|
138
|
+
```sh
|
|
139
|
+
bygone tour schema > /tmp/change-tour-source.schema.json
|
|
140
|
+
```
|
|
141
|
+
|
|
142
|
+
Write a `.bygone` file. The legacy `.bygone.yaml` spelling remains valid when
|
|
143
|
+
generic YAML tooling requires it. Treat either authored source as Git-backed,
|
|
144
|
+
not portable: pin `range.base` and `range.head` to the exact OIDs from the
|
|
145
|
+
context, and keep the file within the corresponding repository so Bygone can
|
|
146
|
+
resolve those objects. Use a compiled `.tour.json` only when a portable
|
|
147
|
+
snapshot is required.
|
|
148
|
+
|
|
149
|
+
For every step:
|
|
150
|
+
|
|
151
|
+
- make one concise explanatory claim;
|
|
152
|
+
- focus an anchor in `base` or `head` evidence;
|
|
153
|
+
- prefer changed lines, using unchanged context only when it establishes a required boundary;
|
|
154
|
+
- use the shortest snippet that is unique within that file and revision;
|
|
155
|
+
- connect behavior to tests, error handling, or other concrete proof;
|
|
156
|
+
- add a connection only when the relationship between two locations materially improves understanding.
|
|
157
|
+
|
|
158
|
+
Never emit generated line numbers or hunk indexes. Verify candidate snippets against the pinned object when uncertain:
|
|
159
|
+
|
|
160
|
+
```sh
|
|
161
|
+
git show HEAD_OID:path/to/file | rg -F -n 'exact snippet'
|
|
162
|
+
```
|
|
163
|
+
|
|
164
|
+
Use `occurrence` only when repetition is intentional and stable. Treat rename identity as evidence rather than describing a rename as unrelated deletion and addition.
|
|
165
|
+
|
|
166
|
+
## Validate and repair
|
|
167
|
+
|
|
168
|
+
Always run validation before presenting or handing off:
|
|
169
|
+
|
|
170
|
+
```sh
|
|
171
|
+
bygone tour validate review.bygone --json
|
|
172
|
+
```
|
|
173
|
+
|
|
174
|
+
Repair every error. Do not weaken, delete, or redirect an anchor merely to make validation pass. If evidence no longer exists, revise the claim or report the broken premise.
|
|
175
|
+
|
|
176
|
+
After structural validation, check that:
|
|
177
|
+
|
|
178
|
+
Treat this as a required self-audit, not a claim the validator can prove. For each item, cite concrete evidence you actually opened or mark it not applicable; the hand-off must distinguish verified findings from interpretation.
|
|
179
|
+
|
|
180
|
+
- the first step establishes enough context for later steps;
|
|
181
|
+
- chapter boundaries follow conceptual transitions rather than a fixed count or one-scene-per-chapter pattern;
|
|
182
|
+
- important production behavior is not hidden in the complete Files rail;
|
|
183
|
+
- tests are connected to the behavior they prove;
|
|
184
|
+
- connections express causal, contractual, data-flow, ordering, or proof relationships;
|
|
185
|
+
- binary files and omitted patches are surfaced explicitly;
|
|
186
|
+
- the final step supplies proof or a clear reviewer conclusion.
|
|
187
|
+
|
|
188
|
+
## Always print the open command
|
|
189
|
+
|
|
190
|
+
Whenever you create, validate, compile, recommend, or open a diff, review, tour, history view, or Git comparison, **always** print the exact one-line `bygone` command the user can paste to open it in the desktop app.
|
|
191
|
+
|
|
192
|
+
Do this even when you also run the command yourself, when presentation was not requested, and when handing off artifacts. Use the real paths and refs from the work; prefer absolute paths when a tour or file lives outside the current directory.
|
|
193
|
+
|
|
194
|
+
| Goal | Command template |
|
|
195
|
+
| --- | --- |
|
|
196
|
+
| Authored tour | `bygone -C <repository> present --tour <path/to/review.bygone>` |
|
|
197
|
+
| Branch review (change set) | `bygone review <head> --base <base>` |
|
|
198
|
+
| App-hosted range tour (no authored file) | `bygone present <head> --base <base>` |
|
|
199
|
+
| Two-way file or directory compare | `bygone <left> <right>` |
|
|
200
|
+
| Explicit diff mode | `bygone --diff <left> <right>` |
|
|
201
|
+
| Multi-panel compare | `bygone <path1> <path2> <path3> [...]` |
|
|
202
|
+
| Git refs compare | `bygone --git-diff <ref1> <ref2> [<ref3>...]` |
|
|
203
|
+
| File or directory history | `bygone --history <path>` |
|
|
204
|
+
| Repo directory history | `bygone` (from inside the Git repo) |
|
|
205
|
+
|
|
206
|
+
Tour tooling that does not open the app (`tour context`, `tour validate`, `tour compile`, `tour coverage`) still warrants the matching open command when a human should inspect the result visually.
|
|
207
|
+
|
|
208
|
+
## Compile or present
|
|
209
|
+
|
|
210
|
+
Compile a portable manifest when the user needs an artifact:
|
|
211
|
+
|
|
212
|
+
```sh
|
|
213
|
+
bygone tour compile review.bygone --output review.tour.json
|
|
214
|
+
```
|
|
215
|
+
|
|
216
|
+
Open the interactive browser only when requested or useful for verifying the result:
|
|
217
|
+
|
|
218
|
+
```sh
|
|
219
|
+
bygone -C /absolute/path/to/repository present --tour review.bygone
|
|
220
|
+
```
|
|
221
|
+
|
|
222
|
+
Always print that same command with the real repository and tour paths, even if you do not run it. `-C` gives Bygone an explicit working directory without changing the user's shell directory.
|
|
223
|
+
|
|
224
|
+
Compiled manifests contain source snapshots. Do not publish or upload them without explicit authorization.
|
|
225
|
+
|
|
226
|
+
## Hand off
|
|
227
|
+
|
|
228
|
+
Report:
|
|
229
|
+
|
|
230
|
+
- the exact base and head OIDs;
|
|
231
|
+
- the **open command** for the primary artifact (`bygone present --tour …`, `bygone review …`, `bygone --git-diff …`, etc.);
|
|
232
|
+
- the source and compiled artifact paths;
|
|
233
|
+
- authored chapter, scene, and step counts, plus compiled counts when the generated complete-change appendix changes them;
|
|
234
|
+
- omitted or unread evidence;
|
|
235
|
+
- validation and visual verification performed;
|
|
236
|
+
- whether generated files are temporary, uncommitted, committed, or pushed.
|
|
237
|
+
|
|
238
|
+
Distinguish syntactic grounding from interpretive correctness: Bygone proves that cited evidence exists at the pinned revision, not that the narrative's interpretation is unquestionably correct.
|
package/standalone/index.html
CHANGED
|
@@ -30,13 +30,13 @@
|
|
|
30
30
|
<div id="change-toolbar" class="change-toolbar header-align-diff" hidden>
|
|
31
31
|
<div class="change-toolbar-main">
|
|
32
32
|
<div class="change-toolbar-nav">
|
|
33
|
-
<button id="previous-file" class="change-button icon-button" type="button" title="
|
|
33
|
+
<button id="previous-file" class="change-button icon-button" type="button" title="Open previous file" aria-label="Previous file">
|
|
34
34
|
<svg viewBox="0 0 24 24" aria-hidden="true">
|
|
35
35
|
<path d="M17 11l-5-5-5 5"></path>
|
|
36
36
|
<path d="M17 18l-5-5-5 5" opacity="0.7"></path>
|
|
37
37
|
</svg>
|
|
38
38
|
</button>
|
|
39
|
-
<button id="next-file" class="change-button change-button-primary icon-button" type="button" title="
|
|
39
|
+
<button id="next-file" class="change-button change-button-primary icon-button" type="button" title="Open next file" aria-label="Next file">
|
|
40
40
|
<svg viewBox="0 0 24 24" aria-hidden="true">
|
|
41
41
|
<path d="M7 13l5 5 5-5"></path>
|
|
42
42
|
<path d="M7 6l5 5 5-5" opacity="0.7"></path>
|
|
@@ -44,7 +44,7 @@
|
|
|
44
44
|
</button>
|
|
45
45
|
</div>
|
|
46
46
|
<div class="change-toolbar-center">
|
|
47
|
-
<button id="previous-change" class="change-button icon-button" type="button" title="Previous difference (Cmd/Ctrl+
|
|
47
|
+
<button id="previous-change" class="change-button icon-button" type="button" title="Previous difference (Shift+F7 or Cmd/Ctrl+Shift+Up)" aria-label="Previous difference">
|
|
48
48
|
<svg viewBox="0 0 24 24" aria-hidden="true">
|
|
49
49
|
<path d="M12 19V5"></path>
|
|
50
50
|
<path d="M6 11l6-6 6 6"></path>
|
|
@@ -65,7 +65,7 @@
|
|
|
65
65
|
<path d="M5 5v14"></path>
|
|
66
66
|
</svg>
|
|
67
67
|
</button>
|
|
68
|
-
<button id="next-change" class="change-button change-button-primary icon-button" type="button" title="Next difference (Cmd/Ctrl+
|
|
68
|
+
<button id="next-change" class="change-button change-button-primary icon-button" type="button" title="Next difference (F7 or Cmd/Ctrl+Shift+Down)" aria-label="Next difference">
|
|
69
69
|
<svg viewBox="0 0 24 24" aria-hidden="true">
|
|
70
70
|
<path d="M12 5v14"></path>
|
|
71
71
|
<path d="M6 13l6 6 6-6"></path>
|
|
@@ -86,7 +86,7 @@
|
|
|
86
86
|
</svg>
|
|
87
87
|
</button>
|
|
88
88
|
</div>
|
|
89
|
-
<div class="change-hint">Cmd/Ctrl+
|
|
89
|
+
<div class="change-hint">F7 / Shift+F7 · Cmd/Ctrl+Shift+Up/Down to jump.</div>
|
|
90
90
|
</div>
|
|
91
91
|
<div id="history-toolbar" class="history-toolbar header-align-diff" hidden>
|
|
92
92
|
<div class="history-side history-side-left">
|
|
@@ -94,14 +94,14 @@
|
|
|
94
94
|
<div id="history-left-time" class="history-time"></div>
|
|
95
95
|
</div>
|
|
96
96
|
<div class="history-nav">
|
|
97
|
-
<button id="history-back" class="history-button icon-button" type="button" title="
|
|
97
|
+
<button id="history-back" class="history-button icon-button" type="button" title="Open older commit (Alt+Left)" aria-label="Older commit">
|
|
98
98
|
<svg viewBox="0 0 24 24" aria-hidden="true">
|
|
99
99
|
<path d="M15 18l-6-6 6-6"></path>
|
|
100
100
|
<path d="M10 18l-6-6 6-6" opacity="0.7"></path>
|
|
101
101
|
</svg>
|
|
102
102
|
</button>
|
|
103
103
|
<div id="history-position" class="history-position" role="status" aria-live="polite" aria-atomic="true"></div>
|
|
104
|
-
<button id="history-forward" class="history-button icon-button" type="button" title="
|
|
104
|
+
<button id="history-forward" class="history-button icon-button" type="button" title="Open newer commit (Alt+Right)" aria-label="Newer commit">
|
|
105
105
|
<svg viewBox="0 0 24 24" aria-hidden="true">
|
|
106
106
|
<path d="M9 18l6-6-6-6"></path>
|
|
107
107
|
<path d="M14 18l6-6-6-6" opacity="0.7"></path>
|
package/web/index.html
CHANGED
|
@@ -51,7 +51,7 @@
|
|
|
51
51
|
<summary id="tour-commits-summary">0 commits</summary>
|
|
52
52
|
<ol id="tour-commits" class="tour-commits"></ol>
|
|
53
53
|
</details>
|
|
54
|
-
<div id="tour-sidebar-resizer" class="tour-sidebar-resizer" role="separator" aria-label="Resize tour sidebar" aria-orientation="vertical" aria-valuemin="240" aria-valuemax="600" tabindex="0"></div>
|
|
54
|
+
<div id="tour-sidebar-resizer" class="tour-sidebar-resizer" role="separator" aria-label="Resize tour sidebar" title="Resize tour sidebar (Left/Right; Home/End)" aria-orientation="vertical" aria-valuemin="240" aria-valuemax="600" tabindex="0"></div>
|
|
55
55
|
</aside>
|
|
56
56
|
<button id="tour-sidebar-show" class="tour-sidebar-show" type="button" title="Show tour sidebar" aria-label="Show tour sidebar" hidden>›</button>
|
|
57
57
|
<section id="tour-narrative" class="tour-narrative" hidden>
|
|
@@ -78,7 +78,7 @@
|
|
|
78
78
|
</div>
|
|
79
79
|
</div>
|
|
80
80
|
</section>
|
|
81
|
-
<div id="tour-narrative-resizer" class="tour-narrative-resizer" role="separator" aria-label="Resize tour header" aria-orientation="horizontal" aria-valuemin="180" tabindex="0"></div>
|
|
81
|
+
<div id="tour-narrative-resizer" class="tour-narrative-resizer" role="separator" aria-label="Resize tour header" title="Resize tour header (Up/Down; Home/End)" aria-orientation="horizontal" aria-valuemin="180" tabindex="0"></div>
|
|
82
82
|
<div class="web-toolbar">
|
|
83
83
|
<div class="web-toolbar-group">
|
|
84
84
|
<button id="web-compare-test" type="button" title="Compare sample files">Compare Test Files</button>
|
|
@@ -113,13 +113,13 @@
|
|
|
113
113
|
<div id="change-toolbar" class="change-toolbar header-align-diff" hidden>
|
|
114
114
|
<div class="change-toolbar-main">
|
|
115
115
|
<div class="change-toolbar-nav">
|
|
116
|
-
<button id="previous-file" class="change-button icon-button" type="button" title="
|
|
116
|
+
<button id="previous-file" class="change-button icon-button" type="button" title="Open previous file" aria-label="Previous file">
|
|
117
117
|
<svg viewBox="0 0 24 24" aria-hidden="true">
|
|
118
118
|
<path d="M17 11l-5-5-5 5"></path>
|
|
119
119
|
<path d="M17 18l-5-5-5 5"></path>
|
|
120
120
|
</svg>
|
|
121
121
|
</button>
|
|
122
|
-
<button id="next-file" class="change-button icon-button" type="button" title="
|
|
122
|
+
<button id="next-file" class="change-button icon-button" type="button" title="Open next file" aria-label="Next file">
|
|
123
123
|
<svg viewBox="0 0 24 24" aria-hidden="true">
|
|
124
124
|
<path d="M7 13l5 5 5-5"></path>
|
|
125
125
|
<path d="M7 6l5 5 5-5"></path>
|
|
@@ -127,7 +127,7 @@
|
|
|
127
127
|
</button>
|
|
128
128
|
</div>
|
|
129
129
|
<div class="change-toolbar-center">
|
|
130
|
-
<button id="previous-change" class="change-button icon-button" type="button" title="Previous difference (Cmd/Ctrl+
|
|
130
|
+
<button id="previous-change" class="change-button icon-button" type="button" title="Previous difference (Shift+F7 or Cmd/Ctrl+Shift+Up)" aria-label="Previous difference">
|
|
131
131
|
<svg viewBox="0 0 24 24" aria-hidden="true">
|
|
132
132
|
<path d="M12 19V5"></path>
|
|
133
133
|
<path d="M6 11l6-6 6 6"></path>
|
|
@@ -148,7 +148,7 @@
|
|
|
148
148
|
<path d="M5 5v14"></path>
|
|
149
149
|
</svg>
|
|
150
150
|
</button>
|
|
151
|
-
<button id="next-change" class="change-button change-button-primary icon-button" type="button" title="Next difference (Cmd/Ctrl+
|
|
151
|
+
<button id="next-change" class="change-button change-button-primary icon-button" type="button" title="Next difference (F7 or Cmd/Ctrl+Shift+Down)" aria-label="Next difference">
|
|
152
152
|
<svg viewBox="0 0 24 24" aria-hidden="true">
|
|
153
153
|
<path d="M12 5v14"></path>
|
|
154
154
|
<path d="M6 13l6 6 6-6"></path>
|
|
@@ -169,7 +169,7 @@
|
|
|
169
169
|
</svg>
|
|
170
170
|
</button>
|
|
171
171
|
</div>
|
|
172
|
-
<div class="change-hint">Cmd/Ctrl+
|
|
172
|
+
<div class="change-hint">F7 / Shift+F7 · Cmd/Ctrl+Shift+Up/Down to jump.</div>
|
|
173
173
|
</div>
|
|
174
174
|
<div id="history-toolbar" class="history-toolbar header-align-diff" hidden>
|
|
175
175
|
<div class="history-side history-side-left">
|
|
@@ -177,14 +177,14 @@
|
|
|
177
177
|
<div id="history-left-time" class="history-time"></div>
|
|
178
178
|
</div>
|
|
179
179
|
<div class="history-nav">
|
|
180
|
-
<button id="history-back" class="history-button icon-button" type="button" title="
|
|
180
|
+
<button id="history-back" class="history-button icon-button" type="button" title="Open older commit" aria-label="Older commit">
|
|
181
181
|
<svg viewBox="0 0 24 24" aria-hidden="true">
|
|
182
182
|
<path d="M15 18l-6-6 6-6"></path>
|
|
183
183
|
<path d="M10 18l-6-6 6-6" opacity="0.7"></path>
|
|
184
184
|
</svg>
|
|
185
185
|
</button>
|
|
186
186
|
<div id="history-position" class="history-position" role="status" aria-live="polite" aria-atomic="true"></div>
|
|
187
|
-
<button id="history-forward" class="history-button icon-button" type="button" title="
|
|
187
|
+
<button id="history-forward" class="history-button icon-button" type="button" title="Open newer commit" aria-label="Newer commit">
|
|
188
188
|
<svg viewBox="0 0 24 24" aria-hidden="true">
|
|
189
189
|
<path d="M9 18l6-6-6-6"></path>
|
|
190
190
|
<path d="M14 18l6-6-6-6" opacity="0.7"></path>
|