helm-charts clearify #57

Closed
opened 2024-01-08 21:32:39 +00:00 by wrenix · 3 comments
wrenix commented 2024-01-08 21:32:39 +00:00 (Migrated from codeberg.org)
huhu @earl-warren you have some question? https://codeberg.org/forgejo-contrib/delightful-forgejo/pulls/49#issuecomment-1409711 if not, close this ticket
earl-warren commented 2024-01-08 21:44:00 +00:00 (Migrated from codeberg.org)

Deploy a Forgejo on the specified instance (default: codeberg.org), name and token (generated .runner config file keeps in a Kubernetes Secret).

Did you mean "Deploy a Forgejo runner..."? Otherwise it would be "Deploy Forgejo" without "a".

> Deploy a Forgejo on the specified instance (default: codeberg.org), name and token (generated .runner config file keeps in a Kubernetes Secret). Did you mean "Deploy a Forgejo runner..."? Otherwise it would be "Deploy Forgejo" without "a".
wrenix commented 2024-01-08 21:49:36 +00:00 (Migrated from codeberg.org)

read over so many times -> of course i mean an runner ;)

read over so many times -> of course i mean an runner ;)
earl-warren commented 2024-01-08 21:56:35 +00:00 (Migrated from codeberg.org)

I suggest you propose a change with just this:

Deploy a Forgejo runner on the specified Forgejo instance (default: codeberg.org).

It clearly explains what it does. Going into details about secrets and names and .runner is best documented in your README.

I suggest you propose a change with just this: > Deploy a Forgejo runner on the specified Forgejo instance (default: codeberg.org). It clearly explains what it does. Going into details about secrets and names and .runner is best documented in your README.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
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: caesar/delightful-forgejo#57
No description provided.