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: documentation/development.md
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,4 +53,15 @@ npm run test:e2e:http:actors
53
53
54
54
## Publishing
55
55
56
-
Publishing is automated in the CI/CD pipeline. Each time a version is release (GitHub ref starting with `refs/tags/v`) then the pipeline will deploy the package as described in [build.yml](./.github/workflows/build.yml).
56
+
Publishing is automated in the CI/CD pipeline. Each time a version is release (GitHub ref starting with `refs/tags/v`) then the pipeline will deploy the package as described in [build.yml](./.github/workflows/build.yml).
57
+
58
+
## Setup GitHub actions
59
+
60
+
1. Fork the [js-sdk](https://github.com/dapr/js-sdk) repo to your GitHub account.
61
+
1. Go to `Settings` in the forked repo and click on `Secrets` -> `Action`:
62
+

63
+
1. Add secret variables for Dapr CI
64
+
65
+
|Secret|Value|Usage|
66
+
|--|--|--|
67
+
|DAPR_BOT_TOKEN|[Your Github Personal Access Token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)|[dapr-bot.yml](https://github.com/dapr/js-sdk/blob/master/.github/workflows/dapr-bot.yml) uses it for administrative actions|
0 commit comments