Feature Request: Needs For Job Steps

[bn-bmagee]

Select Topic Area

Product Feedback

Body

I am not an experienced Github Actions user yet but in my initial foray into workflows I've encountered two instances where it would be beneficial to have a job depend on a specific step in another job. These were:

1. Running three jobs that require setup-go simultaneously. It would be beneficial to be able to load the cache in one job and allow the other two jobs to make use of it. This could be accomplished by having a fourth job load the cache before the other three jobs start, but then you have a job whose sole purpose is to load the cache and all three jobs use it. Perhaps this is efficient but it seems to me having one job not have to reload the cache would be more efficient.
2. Storing an image as an artifact so that another job can depend on having the image and another artifact. In this case I have a particularly long build process and it would be beneficial to start building an image earlier in the process, but in order to make use of it in a separate dependent job I need to, best I can tell, store it as an artifact so that it may be loaded later. Considering that it is needed in only one job it would seem that having that job be the one to create the image would be more beneficial, but then you can't make it start the image creation earlier.

Obviously these are two instances where depending on the job instead of the step is viable, but it seems to me that the build would be faster with this optimization.