Run pipeline from bookmarks and changes, and say why it is unavailable issue #40
closed: completed andymccall opened this · 0 comments
andymccall
Andy's request: starting a pipeline without a check-in should be easy, as on GitLab or GitHub. Make Run pipeline a primary button on the Flow tab and say why it is missing when it is. Add it beside each bookmark and on change pages, the latter running the state whose only head is the change. Accept {"change"} in POST /flow/runs. Runs still only take committed states.
Andy's request: starting a pipeline without a check-in should be easy, as on GitLab or GitHub. Make Run pipeline a primary button on the Flow tab and say why it is missing when it is. Add it beside each bookmark and on change pages, the latter running the state whose only head is the change. Accept
{"change"}inPOST /flow/runs. Runs still only take committed states.