Why is there no Git workflow for non-devs?

Re:Why is there no Git workflow for non-devs? by tarun_anand on Friday April 24, 2020 @10:44PM (#22975114)

Interesting question. I would say that collaborative editing of documents with changelog kind of captures that. For e.g Google Docs.

The checkout, edit, diff, merge, review, build, release workflow might be too onerous for other teams.

Curious to know, why do you ask this question?

[ Parent | on HN ]

Re:Why is there no Git workflow for non-devs? by mesutandtie on Friday April 24, 2020 @11:04PM (#22975216)

Yeah, fair point! I think adaptations can be made. So I'm not a dev, but I've worked on product for a while. Bridging dev workflow and 'rest of business' workflow shows vast inefficiency gaps all over the place for the latter. I feel the trail of decision-making goes missing at the moment too.

This also peaked my curiosity: https://a16z.com/2020/01/09/the-developers-way/ and resonated...a lot haha.

+ something I'd love to see productised/productise myself.

[ Parent | on HN ]

Re:Why is there no Git workflow for non-devs? by rimutaka on Friday April 24, 2020 @11:30PM (#22975306)

The concept of tracking changes, branches, history & blame are pretty universal across different domains and should apply well.

The smallest unit of change in Git is a line (correct me on that), which doesn't work well with something as simple as a text document. E.g. collaboratively working on a ReadMe file on GitHub is quite cumbersome compared to Google Docs or MS Word.

Git is no more than a versioned file repo for CAD or vector files.

It's a reasonable question, though.

[ Parent | on HN ]