Make actions.Job nil return check apply at the job level

Related tasks

Context

Actions currently check that no job function returns nil. This means that no single function (pre-hook, execute or post-hook) can return nil. After some changes to the actions framework, this check at the job function level no longer makes sense because there a now other mechanisms that allow passing state between the different functions of a job.

Change

The requirement to not return a nil value is now only applied at the job level, instead of at the function level. This allows some of the job functions to return nil. The check will now pass as long as the last job function returns a non-nil value.

Other information

Additional documentation