gitea
gitea copied to clipboard
Improve and fix bugs in runner management page
Changes:
- Add no permission to edit tooltip

- fix the logic in ActionRunner.Editable
- Gitea admin user can edit runner in org/repo runner settings page

- Org owner can edit org/repo runner in org's repo runner settings page

- org admin can only edit org's repo runner

- Gitea admin user can edit runner in org/repo runner settings page
- add missed locale word:
runners.task_list.no_tasks - ~~fix overflow of
Recent tasks on this runner~~ This has been fixed. Before:
After:

Edit icon looks slighly misaligned with cross icon horizontally.
![]()
Edit icon looks slighly misaligned with cross icon horizontally.
Done.
@yp05327 Is this PR still relevant? If so, could you update it?
I'll try to update it.
Added individual runner support.
Update is done.
After this, it will be possible to edit a global/org runner on the settings page of a repo if the doer has permission. It doesn't look really good to me.
![]()
![]()
Just my opinion, I would say it could be better to redirect to org/admin settings page.
It seems this hasn't been followed?
This has been supported in https://github.com/go-gitea/gitea/pull/24366/commits/110b928d97b61becf1fc91805d12f1819441bd9e
But I noticed a problem. If admin want to edit a individual runner from admin panel which doesn't belong to him, which URL should we use?
/user/settings/actions/runners/{id} seems strange as this runner doesn't belong to him.
But if we use /admin/actions/runners/{id}, then we have several entry points to this runner ( but for the admin user, there's only one )
Isn't the second option used currently? Looks correct to me, the admin should always use admin routes if possible