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: automation.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
@@ -48,6 +48,23 @@ Content automation is done in the form of adding new JSON files to `records/new`
48
48
4. When the PR is merged (either with _Squash and merge_ or with a merge commit, _Rebase and merge_ is not supported), the [process-json](./.github/workflows/process.yml) workflow will run to perform the requested actions, and when it's done, it will move the processed JSON files to `./records/processed` and renamed the file to `YYYY-MM-DD-ID.json` where ID is an incremental ID based on the number of files already processed on that date. It will also add in additional details of the performed actions (e.g. CID and URI of the posted post).
49
49
5. When the process workflow is complete (likely within a minute), you should see a commit from the GitHub bot in the main branch moving the JSON file.
50
50
51
+
### Threads
52
+
53
+
To send several messages replying to one another, you can separate each tweet
54
+
using a Markdown [thematic break][] inside the `richText` or `richTextFile`:
55
+
56
+
```markdown
57
+
Here is the first tweet.
58
+
59
+
---
60
+
61
+
Here is the second tweet.
62
+
63
+
---
64
+
65
+
Here is the third tweet.
66
+
```
67
+
51
68
## Set up automation in a repository
52
69
53
70
1.[Set up repository secrets](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions#creating-secrets-for-a-repository) for accounts.
@@ -87,3 +104,5 @@ All files starting with .env are ignored in this repository, you could save the
0 commit comments