Ideas for saving pipeline runs in MR's to save resources.

Working on some WIP MR's and was having multiple pipelines run when I was not ready to have pipelines start running, which seemed like a waste of resources to me.

This can also happen when more than one person are collaborating on an MR, and push up work on an MR to get some prelim feedback.

I believe this will save the company A LOT of resources.

How do I see this happening?

• We can look at the title of the MR, maybe have something like NOPIPELINE like we have for WIP: on MR's.
• We can also default it to not running the pipelines, and then someone needs to turn it on to have the pipeline run.
• Pre push hooks for frontend linting
• Create Merge Request/Branch in an issue will cause branch name to fail danger bot if issue title is long.

Relevant Issue Links

• Apply Suggestion commit is too long and danger fails.
• Accepting multiple suggestions at once in an MR.
• Pre push hook guards for frontend devs.
• Create MR via UI fails danger bot
• Reduce Costs of Gitlab Project
• Do not run MR pipelines when master is failing
• Leverage interruptible in GitLab's own pipelines