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: docs/github-workflow.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,3 +16,15 @@ This is a manual step, until automation is ready:
16
16
- create a new one at https://github.com/settings/tokens, required scopes: `repo:status` and `public_repo`
17
17
- the account has to have push access to the test repositories - you will probably want to fork the dependents into that account (or a separate organization)
18
18
- you may want to use a robot account which _does not have **any** merge access_, as Github does not allow restricting tokens to a subset of repositories
19
+
20
+
21
+
## Usage
22
+
23
+
0. This assumes `.wiby.json` is already configured and that you're an owner or a contributor on the dependency repo
24
+
1. Open a PR against the dependency repository
25
+
2. Post a comment saying `wiby test` in the PR
26
+
- This should kick off the test workflow and update the `package.json` of configured dependents
27
+
- Shortly after that, a `wiby` status check will have its status set to `pending`
28
+
3. Wait a reasonable amount of time for the dependents to finish their tests
29
+
4. Post a comment saying `wiby result`
30
+
- Shortly after that, the `wiby` status check will changes its status to report the results of the tests in the dependents (but it may stay pending if they're still running)
0 commit comments