@boxes-dev/dvb-runtime 1.0.1079 → 1.0.1081

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.
@@ -98,6 +98,12 @@ repository, every repository and top-level file inside it starts selected;
98
98
  keep only what belongs in the project in `project.repositories` and
99
99
  `project.rootEntries`.
100
100
 
101
+ When the manifest uses managed GitHub access, `start` also checks whether
102
+ boxes.dev can already use the project's GitHub repositories. If it reports a
103
+ GitHub access problem, run `dvb agent-init github connect` before you
104
+ investigate, so the user can finish on GitHub while you work. `check` verifies
105
+ access again before launch.
106
+
101
107
  Read any worktree, project-overlap, or skipped-repository explanations printed by `start`.
102
108
  Explain them to the user during review and confirm the intended project scope.
103
109
  `check` repeats these explanations in the launch summary; an overlap does not
@@ -122,8 +128,8 @@ The remote thread will use that choice when available on the connected
122
128
  account, with high reasoning where supported.
123
129
 
124
130
  For GitHub repos, the manifest defaults to `githubAccess: managed` and keeps
125
- the seeded GitHub `gitSsh` rows in skip mode. If check says GitHub is not
126
- connected, or that the boxes.dev GitHub App can't access a repository, run
131
+ the seeded GitHub `gitSsh` rows in skip mode. If start or check says GitHub is
132
+ not connected, or that the boxes.dev GitHub App can't access a repository, run
127
133
  `dvb agent-init github connect`, have the user finish in the browser, and then
128
134
  re-run check. Once GitHub is connected, that command opens GitHub and prints
129
135
  which account the user should choose. If an installation needs an update,