+ [2020-07-07T18:43:04Z] bleb why is that
+ [2020-07-07T18:46:07Z] bleb well at any rate i was able to break their security
+ [2020-07-07T19:21:46Z] mydog2 hi....
+ [2020-07-07T19:22:21Z] mydog2 "gh" is the github cli.. my question has to do with the config.yml file...
+ [2020-07-07T19:23:09Z] mydog2 the ~/.config/gh/config.yml <<< dir/file isn't part of the rpm/install.. do I just create this on my own?

message no. 183040

Posted by mydog2 in #github at 2020-07-07T11:10:56Z

var utilities = require('laravel-elixir/ingredients/commands/Utilities'); <<<
+ [2020-07-08T03:54:29Z] twb Is there a way to advise git that a branch is purely historical, without outright deleting the branch?
+ [2020-07-08T04:00:32Z] twb Really just that I had this little repo and github was like "2 branches" and I went "WTF there should only be master... oh it's that merge branch from ages ago"
+ [2020-07-08T04:00:46Z] twb To make that not happen :-)
+ [2020-07-08T04:01:39Z] twb What I do at the moment for my big repos is to have a separate "attic" repo, svn style, and keep all the historical branch names there, but aggressively delete them from the main repo