@boxes-dev/dvb-runtime 1.0.1113 → 1.0.1115

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.
@@ -161,8 +161,11 @@ account, with high reasoning where supported.
161
161
 
162
162
  For GitHub repos, the manifest defaults to `githubAccess: managed` and keeps
163
163
  the seeded GitHub `gitSsh` rows in skip mode. If start or check says GitHub is
164
- not connected, run `dvb agent-init github connect`, have the user finish in the
165
- browser, and then re-run check.
164
+ not connected, run `dvb agent-init github connect` in the background and have
165
+ the user finish in the browser. It waits until boxes.dev can access the
166
+ project's repositories, which can take several minutes; re-run check when it
167
+ succeeds. If it stops after 20 minutes without progress, for example while an
168
+ organization owner reviews the request, run it again once the user is ready.
166
169
 
167
170
  If the boxes.dev GitHub App can't access a repository, ask the user how the
168
171
  project should pull and push. App access needs the App installed for the
@@ -170,8 +173,9 @@ repository's owner, and an organization owner may need to approve it. SSH uses
170
173
  a key added to the user's own GitHub account. Either one covers pull and push;
171
174
  automatic pull request updates and follow-ups need App access. With SSH, the
172
175
  user can give the App access later for those features and keep SSH for pull
173
- and push. For App access, run `dvb agent-init github connect`; it opens GitHub
174
- and prints which account the user should choose. If an installation needs an
176
+ and push. For App access, run `dvb agent-init github connect` in the
177
+ background; it opens GitHub, prints which account the user should choose, and
178
+ waits for the user to finish there. If an installation needs an
175
179
  update, follow the exact action printed by check. Set `githubAccess: ssh` and
176
180
  the GitHub `gitSsh` rows to setup only when the user chooses SSH, and keep the
177
181
  user's choice when access changes later. GitLab and other origins continue to