Skip to content

Commit 47e1012

Browse files
author
nanos
committed
try more
1 parent 953d9f3 commit 47e1012

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

README.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -56,9 +56,12 @@ Regardless of how you want to run FediFetcher, you must first get an access toke
5656

5757
### 2) Configure and run FediFetcher
5858

59-
You can run FediFetcher as a GitHub Action, a cron job, a container, or a systemd timer. Choose whichever is the most suitable for you (if you are not sure, I suggest trying the GitHub Action).
59+
You can run FediFetcher as a GitHub Action, a cron job, a container, or a systemd timer. Choose whichever is the most suitable for you (if you are not sure, I suggest trying the GitHub Action):
6060

61-
#### To run FediFetcher as a GitHub Action:
61+
<details>
62+
<summary>
63+
<h4 id="to-run-fedifetcher-as-a-github-action">To run FediFetcher as a GitHub Action:</h4>
64+
</summary>
6265

6366
1. Fork this repository
6467
2. Add your access token:
@@ -71,7 +74,7 @@ You can run FediFetcher as a GitHub Action, a cron job, a container, or a system
7174
> [!NOTE]
7275
>
7376
> Keep in mind that [the schedule event can be delayed during periods of high loads of GitHub Actions workflow runs](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#schedule).
74-
77+
</details>
7578
<details>
7679
<summary>
7780
<h4 id="to-run-fedifetcher-as-a-github-action">To run FediFetcher as a cron job:</h4>

0 commit comments

Comments
 (0)