the hubotApprove step should really create a nested input step to ensure that the IDs always match and to make the DSL simpler and more groovy

[jstrachan]

no idea yet how one Jenkins Step can create another one internally yet ;) But if we can figure that out it will remove some noise.

e.g. instead of this:

hubotApprove "Do you want to stage?"
input id: 'Proceed', message: "Do you want to stage?"

we could just use

hubotApprove "Do you want to stage?"

[nrayapati]

@jstrachan Recently I have released a plugin which does combine these two steps together, just in case if you still wondering about how can we create another one internally.

https://github.com/jenkinsci/hubot-steps-plugin