Past status of diabled jobs is referenced on restart

[yakanechi]

What happened:
For example, the following pipeline is executed once
After that, "first2" is disabled and restarted from "first1".

In the current specification, "second" is triggered by reference to the past status of "first2", despite first2 being disabled.

This specification seems a bit strange to me.
The user should assume that "second" jobs and subsequent jobs that have "second" job as a trigger will also not be triggered because of the fact that it is disabled.

What you expected to happen:
Do not refer to the past status of disabled job.

How to reproduce it:
<- Start, Resart ->

jobs:
  first1:
    requires: [ ~commit ]
  first2:
    requires: [ ~commit ]
  second:
    requires: [ first1, first2 ]

[VonnyJap]

@yakanechi @kumada626 - after discussing with others, we feel that this is the right implementation for the case of restart. The second job is restarted as the downstream effect after first1 restarted and even though the first2 is now disabled, it had been previously run in the parent event. So we conclude this should be the expected behavior.

[yakanechi]

@VonnyJap
Thanks for the reply. I'm comfortable with that conclusion.
In that case, it looks good because it consistently inherits the parent status.