pub const NIX_DESTINATIONS: [&str; 3];Expand description
The destinations of the opt-in Nix capability, present in a projection
only where the landing’s nix parameter is on.
The parameter is recorded, so status, upgrade, and adopt can
reconstruct whether these files are supposed to exist: an absent file
under nix = false is not wanted, never drifted.
The capability lands no workflow, on either forge, and each forge’s reason is its own. On GitHub a job gates the merge only inside the workflow the required check needs, and that workflow is the target’s own. On GitLab the merge check is the whole pipeline, and a target’s jobs live in the child pipeline the rendered parent triggers, which the target owns. The bindings serve the job for both.