When project is forked, it will have same set of triggers, and you may do not want some triggers firing. For instance, the trigger to automatically sync onedev/server to its github mirror.

When project is forked, all source code is copied and so the onedev-buildspec.yml including jobs and theirs triggers.

The fork project will trigger is own job, not the job of the source project forked ? Maybe you design this features for performance concern ?

Then, why a project name selection instead of checkbox saying "disable trigger when forking ?"

All triggers and jobs are defined in .onedev-buildspec.yaml. There is no notion of triggering job of other projects here. Project fork is just an example, it may not be a fork at all (for instance clone a project and push under a different name, etc.)

i find the option a bit confusing or not very usefull...

At least, thanks for the light, i close the thread.