Since 10.6 Actions are disabled by default unless the actions.enabled is set to true (which deploys an ACT Runner) #731

New Issue

2024-11-27T07:39:22Z

Gui13 commented

2024-11-27 07:39:22 +00:00

(Migrated from gitea.com)

Since version 10.6.0, my external runner was failing to login to Gitea.

I found out that the configuration value in app.ini for [actions] has been added with a default value of ENABLED=false, whereas in versions 10.5 and earlier Gitea was taking the default value (which is true).

I think it makes sense to tell people in the chart Readme that to activate the Actions they now have to manually set the ENABLED: true in the chart config values like so:

config:
  # [... ]
  actions:
    ENABLED: true

Since version 10.6.0, my external runner was failing to login to Gitea. I found out that the configuration value in app.ini for [actions] has been added with a default value of ENABLED=false, whereas in versions 10.5 and earlier Gitea was taking the default value (which is true). I think it makes sense to tell people in the chart Readme that to activate the Actions they now have to manually set the `ENABLED: true` in the chart config values like so: ```yaml config: # [... ] actions: ENABLED: true ```

Gui13 commented

2024-11-27 07:58:00 +00:00

(Migrated from gitea.com)

I want to reopen, the ticket was automatically closed when I started my PR

Gui13 commented

2024-11-27 12:12:00 +00:00

(Migrated from gitea.com)

Is there a bug? I can't reopen the issue when I click to write a comment. I have to resort to tab-tab-tab until reaching the text area.. sorry for the amount of comments here

justusbunsi commented

2024-11-27 16:56:40 +00:00

(Migrated from gitea.com)

@Gui13

Is there a bug? I can't reopen the issue when I click to write a comment. I have to resort to tab-tab-tab until reaching the text area.. sorry for the amount of comments here

Not sure. You could try reproducing this on demo.gitea.com. Maybe it got closed due to committing on main of your fork. That would be a huge bug which should be reported in Gitea repo itself.

@Gui13 >Is there a bug? I can't reopen the issue when I click to write a comment. I have to resort to tab-tab-tab until reaching the text area.. sorry for the amount of comments here Not sure. You could try reproducing this on demo.gitea.com. Maybe it got closed due to committing on main of your fork. That would be a huge bug which should be reported in Gitea repo itself.

justusbunsi commented

2024-11-27 17:00:19 +00:00

(Migrated from gitea.com)

Regarding the actual issue you reported: Uff, you are right. I forgot that actions are enabled by default when the runner feature was introduced. Thanks for reporting. From a semver point of view, 10.6 should've been a major release with breaking changes as 11.0.

justusbunsi commented

2024-11-27 17:15:58 +00:00

(Migrated from gitea.com)

Regarding the tab-tab-tab textarea topic: I now know what you mean. That's for sure a bug. (writing this with GitNex client)

justusbunsi commented

2024-11-27 20:22:49 +00:00

(Migrated from gitea.com)

By the way, I updated the 10.6 release text to inform users about the unintended breaking change.

justusbunsi commented

2024-11-27 20:27:00 +00:00

(Migrated from gitea.com)

Regarding the tab-tab-tab textarea topic: I now know what you mean. That's for sure a bug. (writing this with GitNex client)

Instance has been updated to fix the texarea issue. Thanks @lunny.

> Regarding the tab-tab-tab textarea topic: I now know what you mean. That's for sure a bug. (writing this with GitNex client) Instance has been updated to fix the texarea issue. Thanks @lunny.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: lunny/helm-chart#731