+ [2020-03-12T18:17:41Z] avuncular I /think/ the history isn't screwed up
+ [2020-03-12T18:17:55Z] avuncular The network graph seems sensible
+ [2020-03-12T18:18:09Z] dmlloyd then you're probably fine
+ [2020-03-12T18:18:29Z] avuncular Cool, will give that a try. Thanks @dmlloyd!
+ [2020-03-12T18:18:56Z] dmlloyd for future reference though, github is more intuitive with branches that are periodically rebased on upstream than with branches that are periodically merged with upstream

message no. 177665

Posted by avuncular in #github at 2020-03-12T18:06:30Z

Hm, did we do something github-wrong here? All of these keep showing up as merge commits. We can't squash them via a merge commit.
+ [2020-03-13T09:38:47Z] DK21 i want to integrate this commit into my foreman installation: https://github.com/theforeman/foreman/pull/7482/commits/246fe36a03882e8ca68ae2cf3b1193017f5b8e03 how would i actually do that?
+ [2020-03-13T09:41:30Z] roboirc you may have to just git clone the code with that commit and use it
+ [2020-03-13T09:41:39Z] roboirc or check this
+ [2020-03-13T09:41:40Z] roboirc https://stackoverflow.com/questions/6372044/how-do-i-merge-a-specific-commit-from-one-branch-into-another-in-git
+ [2020-03-13T16:27:46Z] Tiders Have issue templates in my repo. They were created using the github tool in settings page to generate them. They'd been working but just suddenly in the last day or 2 the body content of the template no longer gets put into new issues. The asignee and labels are still auto set but the body content is not put in. Anyone else come accross this issue?