+ [2019-12-02T21:58:15Z] Intelo Hi
+ [2019-12-02T21:58:47Z] Intelo If I have 2 branches. 2nd branch is ahead with 10 commits. If I merge back in 1st branch, can I just show ONE commit in 1st branch after merge rather than 10? I mean that 1 commit will have all data of those 10 commits (the diff)? So those 10 commits do not ever show in the 1st branch
+ [2019-12-02T22:06:53Z] tang^ look up git merge squash
+ [2019-12-02T22:07:02Z] tang^ !squash
+ [2019-12-02T22:07:13Z] Intelo thanks

message no. 176211

Posted by mertyildiran in #github at 2019-12-02T18:43:34Z

I know there is https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds but seems like it's for the jobs in the same workflow while the thing I need is a check across different workflows.
+ [2019-12-03T02:02:31Z] OnkelTem Hi folks. I wonder is there any statistics about at what degree GitHub is a cemetary of dead projects?
+ [2019-12-03T02:50:57Z] nedbat OnkelTem: define "dead"
+ [2019-12-03T02:51:28Z] nedbat OnkelTem: and also, what would it mean if it were?
+ [2019-12-03T03:22:30Z] nate OnkelTem: Considering all the private repos, probably not
+ [2019-12-03T03:23:06Z] nate Or at minimum even factoring them it would probably skew results a lot for people who setup repos for future plans but don't end up doing anything with it