Skip to content

Commit a4f5fb0

Browse files
authored
Merge pull request #8 from chairulakmal/main
fix: clarify README to state that users only need to add secrets
2 parents e958b16 + 27a8a90 commit a4f5fb0

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

README.md

+3-4
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,11 @@ This GitHub Action automates the build and deployment process for [Minifront](ht
66

77
1. **Fork this repository** to your own GitHub account.
88

9-
2. **Customize the Action**. Modify the `.github/workflows/deploy-minifront.yml` file:
10-
- Fill in environment variables for your desired hosting providers. You can use as many as you like, they will all be deployed sequentially.
11-
- Update the secrets in your GitHub repository accordingly.
9+
2. **Add Environment Secrets**. You do not need to customize the `.github/workflows/deploy-minifront.yml` file. Simply add the necessary environment [secrets](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions) in your GitHub repository for your desired hosting providers:
10+
- You can use as many as you like, they will all be deployed sequentially.
1211
- Providers without configured secrets won't run.
1312
- Github Pages are deployed automatically, but need to be enabled in your repository settings.
14-
- Change cron frequency as desired (given github free tier, you can deploy at most every 4 hours)
13+
- Change cron frequency as desired (given GitHub free tier, you can deploy at most every 4 hours).
1514

1615
3. **Enable GitHub Actions**. Make sure GitHub Actions are enabled in your forked repository (Settings > Actions > General).
1716

0 commit comments

Comments
 (0)