Document what per-branch' "Protected file patterns" actually means #479

New issue

Open

opened 2024-10-17 21:17:34 +02:00 by fogti · 1 comment

fogti commented

2024-10-17 21:17:34 +02:00

Settings > Branches > (on a branch (pattern)) [Edit] > Protected file patterns does apparently block all interaction with a file / directory tree, but it is not obvious how this should be used.
In general / practical application, for many scenarios, it would be beneficial to have something like CODEOWNERS (apparently supported by forgejo (see also: gitea.nulo.in/Nulo/forgejo@605f3a21a4), although I couldn't find out, what the overall consequences are / wasn't able to find any documentation); and restrict merging privileges to those (optionally?).

cc @mikolaj

`Settings > Branches > (on a branch (pattern)) [Edit] > Protected file patterns` does apparently block all interaction with a file / directory tree, but it is not obvious how this should be used. In general / practical application, for many scenarios, it would be beneficial to have something like `CODEOWNERS` (apparently supported by forgejo (see also: https://gitea.nulo.in/Nulo/forgejo/commit/605f3a21a433f72f7994915aebc02eb205843693), although I couldn't find out, what the overall consequences are / wasn't able to find any documentation); and restrict merging privileges to those (optionally?). cc @mikolaj