Add the ability to augment onPush with the default value.

[ursi]

I have a flake with legacyPackages that I wanted test. I figured I could add a separate onPush.legacyPackages for them so I could define how to build them, but the way the code currently works, if you provide your own onPush, it gets rid of the defaults. I would like there to be a way where I could choose to keep the default value, and augment it with my own.

[roberth]

I could add a function in the herculesCI arguments so you can access the translation from flake outputs to nested attrsets and manipulate it in any way.
Here's an example of how this new feature idea may be used:

  herculesCI = { flakeOutputs, ... }: {
    onPush.default = {
      outputs = { ... }:
        flakeOutputs self // {
          # Attributes here will be built for each push.
          legacyPackages = ...;
        };
    };
  };

I'd also like to offer an easier interface as part of a flake.parts module.

[Kranzes]

How would flake parts improve this situation?

[roberth]

Recent versions of hercules-ci-effects include a flakeModule that replaces the default herculesCI attribute in the flake by one that's managed through the module system. Like the agent's built-in functionality, it provides a herculesCI.onPush.default job, and thanks to a custom type, herculesCI.onPush.default.outputs supports merging.
This should solve the problem at least in projects that use flake-parts.

Example:

herculesCI = { config, ... }: {
  onPush.default.outputs.myCustomAttribute = pkgs.writeText "branch-name" ${config.repo.branch}
};

See config.repo and other options on the page.