Automatically update README.md from action.yml contents (again) #108

Open
opened 2025-11-30 19:05:16 +00:00 by stefangehn · 2 comments

I just noticed that README.md is outdated for a few of the inputs (and their defaults), however the descriptions in action.yml are up-to-date.

Would it maybe be a good idea to reinstate the automatic updating of README.md from the contents of action.yml using the action-docs action mentioned at the end of the readme file?

Please note that doing this would conflict with actions/forgejo-release!102 and possibly other manual edits done in README.md in the past.

I could create a PR for this if desired or (if not desired) try to make the two files consistent again.

I just noticed that README.md is outdated for a few of the inputs (and their defaults), however the descriptions in action.yml are up-to-date. Would it maybe be a good idea to reinstate the automatic updating of README.md from the contents of action.yml using the `action-docs` action mentioned at the end of the readme file? Please note that doing this would conflict with actions/forgejo-release!102 and possibly other manual edits done in README.md in the past. I could create a PR for this if desired or (if not desired) try to make the two files consistent again.
Author

FWIW, the current diff if you run action-docs --update-readme is:

diff --git i/README.md w/README.md
index f00e8bc..b13d8a4 100644
--- i/README.md
+++ w/README.md
@@ -10,12 +10,12 @@ Upload or download the assets of a release to a Forgejo instance.
 
 | name | description | required | default |
 | --- | --- | --- | --- |
-| `url` | <p>URL of the Forgejo instance</p> | `false` | `${{ env.GITHUB_SERVER_URL }}` |
-| `repo` | <p>owner/project relative to the URL</p> | `false` | `${{ github.repository }}` |
-| `tag` | <p>Tag of the release</p> | `false` | `${{ github.ref_name }}` |
+| `url` | <p>URL of the Forgejo instance</p> | `false` | `${{ env.FORGEJO_SERVER_URL }}` |
+| `repo` | <p>owner/project relative to the URL</p> | `false` | `${{ forge.repository }}` |
+| `tag` | <p>Tag of the release</p> | `false` | `${{ forge.ref_name }}` |
 | `title` | <p>Title of the release (defaults to tag)</p> | `false` | `""` |
-| `sha` | <p>SHA of the release</p> | `false` | `${{ github.sha }}` |
-| `token` | <p>Forgejo application token (must have `write:repository`)</p> | `false` | `${{ secrets.GITHUB_TOKEN }}` |
+| `sha` | <p>SHA of the release</p> | `false` | `${{ forge.sha }}` |
+| `token` | <p>Forgejo application token</p> | `false` | `${{ forge.token }}` |
 | `release-dir` | <p>Directory in whichs release assets are uploaded or downloaded</p> | `true` | `""` |
 | `release-notes` | <p>Release notes</p> | `false` | `""` |
 | `direction` | <p>Can either be <code>download</code> or <code>upload</code></p> | `true` | `""` |
FWIW, the current diff if you run `action-docs --update-readme` is: ```patch diff --git i/README.md w/README.md index f00e8bc..b13d8a4 100644 --- i/README.md +++ w/README.md @@ -10,12 +10,12 @@ Upload or download the assets of a release to a Forgejo instance. | name | description | required | default | | --- | --- | --- | --- | -| `url` | <p>URL of the Forgejo instance</p> | `false` | `${{ env.GITHUB_SERVER_URL }}` | -| `repo` | <p>owner/project relative to the URL</p> | `false` | `${{ github.repository }}` | -| `tag` | <p>Tag of the release</p> | `false` | `${{ github.ref_name }}` | +| `url` | <p>URL of the Forgejo instance</p> | `false` | `${{ env.FORGEJO_SERVER_URL }}` | +| `repo` | <p>owner/project relative to the URL</p> | `false` | `${{ forge.repository }}` | +| `tag` | <p>Tag of the release</p> | `false` | `${{ forge.ref_name }}` | | `title` | <p>Title of the release (defaults to tag)</p> | `false` | `""` | -| `sha` | <p>SHA of the release</p> | `false` | `${{ github.sha }}` | -| `token` | <p>Forgejo application token (must have `write:repository`)</p> | `false` | `${{ secrets.GITHUB_TOKEN }}` | +| `sha` | <p>SHA of the release</p> | `false` | `${{ forge.sha }}` | +| `token` | <p>Forgejo application token</p> | `false` | `${{ forge.token }}` | | `release-dir` | <p>Directory in whichs release assets are uploaded or downloaded</p> | `true` | `""` | | `release-notes` | <p>Release notes</p> | `false` | `""` | | `direction` | <p>Can either be <code>download</code> or <code>upload</code></p> | `true` | `""` | ```
Owner

yes. please send a pr. probably include a CI check which fails on diff would be a good thing to not forget in future

yes. please send a pr. probably include a CI check which fails on diff would be a good thing to not forget in future
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
actions/forgejo-release#108
No description provided.