>Absolutely. By why 'ought'? What's stopping you? I don't know of any decent tools. Something that would give an end user a nice UI to let them edit a markdown

>Absolutely. By why 'ought'? What's stopping you? I don't know of any decent tools. Something that would give an end user a nice UI to let them edit a markdown or JSON/YAML file and issue a pull request following a team defined workflow, for example? Or a WYSIWYG markdown editor that can issue pull requests following a team defined workflow at the click of a button? >Git has an API I noticed. >I am almost positive this already exists in many various forms online Most teams I've worked with don't have anything. One of the first things I do when I join a team is figure out their workflows (typically baked into people's heads) and get them down in a script. >It breaks down, IMO, because of environmental constraints. You're trying to maintain alias sets across machines A) git aliases are a poor substitute for a decent workflow program. B) A lot of workflows integrate a lot of different things - e.g. by convention, branch names on new tickets often contain the JIRA ticket number followed by a slugified name. That means to properly script a workflow you need to make an API call to get a ticket number and slugify the name and use it to create the new branch.