Triggers (Automation)
Most of triggers only work inside a Git repository. Make sure you initialize a repository if you want to take advantage of them.
For now, this operation overwrites the .git/hooks folder. Be sure to move your manually defined hooks elsewhere before enabling pipelight hooks.
The listener remains easy on the OS and consumes very few resources by once again using the kernel modules through Rust's most used crates.
When triggers are added to a pipeline, the pipeline is not triggered until the triggering requirements are met. Which means that you need to checkout to the allowed branches or tags, and execute the allowed actions for the pipeline to be executed.
Branches are your git project branches names (see: git branch). Tags are the commits you made with git tag -a "v0.8" (see: git tag).
Actions are named according to git-hooks names, plus special flags "manual", "watch" and "blank".
:focal(1800x1210:0x0)/cloudfront-us-east-2.images.arcpublishing.com/reuters/MYYE4IDMZVLXVLDZRNOVBQGCAU.jpg)
