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
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -162,15 +162,15 @@ Customize the workflow to your needs!
162
162
163
163
## How to setup Squads integration:
164
164
165
-
In general its recommended to use the [Squads Multisig](https://docs.squads.so/squads-cli/overview) to manage your programs.
165
+
In general its recommended to use the [Squads Multisig](https://docs.squads.so/main/getting-started/create-a-squad) or any other multisig plattform to manage your programs.
166
166
It makes your program deployments more secure and is considered good practice.
167
167
168
168
1. Setup a new squad in [Squads](https://v4.squads.so/squads/) then transfer your program authority to the squad.
2. Add your local keypair to the squad as a member (At least needs to have voter permissions) so that you can propose transactions. And also add that keypair as a github secret.
173
+
2. Add your local keypair to the squad as a member (At least needs to have voter permissions) so that it can propose transactions. And also add that keypair as a github secret.
174
174
To run it locally add the following to your .secrets file:
2. Add the following to your .secrets file if you want to run it locally or add them to your github secrets if you want to run it in github actions:
184
+
2. Add the multisig information to your `.secrets` file if you want to run it locally or add them to your github action secrets (Not workflow secrets) if you want to run it in github actions:
0 commit comments