Create a fork of binderhub to develop opt-out feature of not launching following build/push

[consideRatio]

Update

Fork and development branch, together with a draft PR is now found at jupyterhub/binderhub#1647.

[yuvipanda]

Can you tell me what you mean by a 'fork' in this context?

[consideRatio]

I mean a github repository fork of jupyterhub/binderhub to develop and trial the feature to upstream to jupyterhub/binderhub after success.

[yuvipanda]

I would love for us to have a WIP PR on the binderhub repo from the start, primarily to make sure we don't end up writing code that is not acceptable to be merged. The smaller the diffs, the better. However, we do not need to wait for those to first get merged before continuing testing.

For this specifically, I would suggest a traitlet that adds a conditional to not launch.

[consideRatio]

We are in agreement on the importance of getting feedback on the proposed change as quick as possible!

I ended up formulating this as a goal as I want to ensure that I can build the Dockerfile referencing a fork's branch meanwhile waiting for feedback and approval of the upstream PR.

[consideRatio]

I've opened jupyterhub/binderhub#1647 as a placeholder PR, and used my personal repo consideratio/binderhub as a fork - but the PR branch can be pushed to by jupyterhub/binderhub maintainers.

This is what's relevant to facilitate Dockerfile creation etc to unblock #3.