+ [2020-05-21T18:36:54Z] tetrakist Thanks, nedbat
+ [2020-05-21T19:29:52Z] canton7 Lewix, as in, the tooling we use for reviews has a harder time if one version of a commit is reviewed, then that's rewritten post-review
+ [2020-05-21T19:30:25Z] canton7 Lewix, (to be honest, I don't know of any tooling which handles that perfectly, since the commit that was reviewed as unavoidably changed, although some handle it better than others)
+ [2020-05-21T23:52:44Z] gp I am trying to post yaml data to the api linter with application/x-yaml mimetype but that isn't supported. what type should I use?
+ [2020-05-21T23:55:19Z] gp doh nm I realized I read it wrong - it expects the content string in a json object

message no. 180836

Posted by canton7 in #github at 2020-05-21T08:20:26Z

Lewix, depends. We use rebasing for feature branches before they go into review, because it's a bit easier to fix up merge conflicts bit-by-bit, and it keeps the history cleaner for the reviewers. Once it's been reviewed we switch to merge-only, because otherwise the history of the review gets muddled between old and new versions of the commits
+ [2020-05-22T01:17:40Z] InnovAnon-Inc what's the recommended way to release artifacts on github? ghr and github-release aren't doing it for me
+ [2020-05-22T01:26:44Z] nedbat InnovAnon-Inc: you know people here will ask the same queestion as in #git
+ [2020-05-22T01:27:14Z] nedbat InnovAnon-Inc: does the release already exist?
+ [2020-05-22T01:38:25Z] InnovAnon-Inc no I need CircleCI to create the release and push the artifacts
+ [2020-05-22T01:38:42Z] InnovAnon-Inc the #git channel told me to come here