instabox 0.8.74 → 0.8.76
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/cli/SHA256SUMS +6 -6
- package/cli/instabox-darwin-amd64 +0 -0
- package/cli/instabox-darwin-arm64 +0 -0
- package/cli/instabox-linux-amd64 +0 -0
- package/cli/instabox-linux-arm64 +0 -0
- package/cli/instabox-windows-amd64.exe +0 -0
- package/cli/instabox-windows-arm64.exe +0 -0
- package/package.json +1 -1
- package/skills/instabox/SKILL.md +1 -1
package/cli/SHA256SUMS
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
|
-
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
1
|
+
b71d3d7c52ecef9f30c12e9635c7bcbae7f1a28dbec9d278cf112482dd885f91 instabox-darwin-amd64
|
|
2
|
+
3698aaf6de34a5f2c2b202e43d54e8cb9d5eaca32ebb797d11bfa09f8581503a instabox-darwin-arm64
|
|
3
|
+
97b8953ea6b4cb36599c0b53866694b860600f1b26b00589877c2bdb5f73c6a8 instabox-linux-amd64
|
|
4
|
+
62e9b5484b12e570c47456c392eac7f166e69c3f7c8c18b234228b5f39571d82 instabox-linux-arm64
|
|
5
|
+
3367b06ab7900ede5c3b26f20eb759ba06257e1db4b7a529d09a356e6d7abea0 instabox-windows-amd64.exe
|
|
6
|
+
9fb0190578037a7f400f071a1cf0e047a11993eb1e0f64c8888d5f36c454a677 instabox-windows-arm64.exe
|
|
Binary file
|
|
Binary file
|
package/cli/instabox-linux-amd64
CHANGED
|
Binary file
|
package/cli/instabox-linux-arm64
CHANGED
|
Binary file
|
|
Binary file
|
|
Binary file
|
package/package.json
CHANGED
package/skills/instabox/SKILL.md
CHANGED
|
@@ -162,7 +162,7 @@ Every `webhooks` subcommand takes `--json` (or `-o json`).
|
|
|
162
162
|
When the user asks to run their CI on instabox, set up `runs-on: instabox-medium` in their repo, end to end. Each job then runs on a fresh Ubuntu 24.04 box (like `ubuntu-latest`) that is deleted when the job ends.
|
|
163
163
|
|
|
164
164
|
1. Get OWNER/REPO: `gh repo view --json owner,name,visibility --jq '.owner.login+"/"+.name+" "+.visibility'`. If it's public, tell the user that pull requests from forks will run on their workspace too, on their plan, and that GitHub's **Require approval for all external contributors** (the repository's **Settings** > **Actions** > **General**) makes each one wait for their approval. Then run `instabox ci` (with `--org ORG` for a workspace): if it says GitHub Actions jobs aren't open on this account yet, use the CLI way below instead.
|
|
165
|
-
2. Pick the workspace that runs and pays for the jobs: when `instabox workspace ls` lists more than one, ask the user which. Send them the App link with its ID, https://dashboard.instabox.sh/auth/github-app/install?org=ORG_ID (without `?org=`
|
|
165
|
+
2. Pick the workspace that runs and pays for the jobs: when `instabox workspace ls` lists more than one, ask the user which. Send them the App link with its ID, https://dashboard.instabox.sh/auth/github-app/install?org=ORG_ID (without `?org=` the page asks which workspace when they are in more than one). Linking takes an owner or admin of that workspace. Ask them to install the App on OWNER, give it access to REPO and link it, and wait until they say it's done. The page it ends on names the workspace it linked. If it says "your personal workspace" and they meant another, see the end of this section. You can't do this step for them.
|
|
166
166
|
3. Change `runs-on:` of the jobs to move to `instabox-medium` (4 vCPU / 8 GiB), or `instabox-small` (2 / 4) or `instabox-large` (8 / 16) where the plan has them (the free plan runs `instabox-medium` only; any other `instabox` label, `instabox` alone included, is refused). Leave the steps alone; the jobs' secrets stay GitHub Actions secrets, as the box gets none of the user's instabox secrets.
|
|
167
167
|
4. Show the user the diff and push only with their OK.
|
|
168
168
|
5. Check the first run: `gh run watch`, and `instabox ci` (with `--org ORG` for a workspace) shows each job's state and why it waits or was refused. When nothing is linked, `instabox ci` says so and prints the App install link to send. A job that stays queued on GitHub with nothing in `instabox ci` means the App has no access to REPO; go back to step 2.
|