Rerun this build button should also include the lane to run

[KrauseFx]

If you change the lane to run of a project, and re-trigger a historic build, we should use all the attributes used to trigger the build, including any parameters and the lane to run

[taquitos]

Ah, so if you re-trigger a historic build it should do exactly the same thing as the original, not using the new config, right?

[KrauseFx]

I think it very much depends on what we call this button. Right now it's called Re-run for this commit, so it would be fine. But if we have a Rerun button, I think we should at least show a summary of the parameters that are gonna be used (lane, variables, git sha) and the user can confirm, to be very clear/transparent about it 👍

We can decide later on how this might look like, just something to be aware of before the 1.0 release

[fastlane-danger-bot]

We decided to pause our work on fastlane.ci to focus on the core fastlane product as we have a lot on the roadmap. You can find more information on the main GitHub page. This issue will be auto-closed 👍