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: README.md
+19Lines changed: 19 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,9 +15,14 @@ For the workflow you just need to set `use-squads` to true and add the needed se
15
15
- ✅ Compute budget optimization
16
16
- ✅ Retry mechanisms for RPC failures
17
17
- ✅ Running anchor tests
18
+
- ✅ Caching for faster reruns for all installs
19
+
- ✅ Extend program automatically
20
+
18
21
19
22
### How to use
20
23
24
+
Create a Solana Program. Either a [native program](https://solana.com/de/developers/guides/getstarted/local-rust-hello-world) and an [anchor program](https://www.anchor-lang.com/docs/quickstart/local). The program with the `anchor.toml` and/or `cargo.toml` need to be in the root of your repository for these workflows to work out of the box.
25
+
21
26
```yaml
22
27
name: Devnet Build and Deploy
23
28
@@ -202,6 +207,20 @@ The MULTISIG is the address of the multisig you want to use this one you can fin
202
207
203
208
What this workflow will do is write a program and an IDL buffer for your program and then propose a transaction that you can approve in the Squads UI.
204
209
210
+
Once the build was successful you can see the program upgrade transaction in your squads ui:
### Additional step for verification when using squads
216
+
217
+
When you use squads to deploy your program after you approved the transaction to deploy your program you need to still trigger a remote job of the Ottersec api for it to actually show up in the solana explorer:
0 commit comments