+ [2020-03-06T19:41:53Z] Soliton unless the latest release has just happened what you get from cloning is not the latest release.
+ [2020-03-06T19:43:21Z] Soliton there is also no reason every tag is a release or whatever logic github uses there.
+ [2020-03-06T20:35:05Z] jlk there is no standard way. Developers can use a wide array of methods to version their software.
+ [2020-03-06T21:08:10Z] R2robot I prefer semantic versioning https://semver.org/
+ [2020-03-06T21:08:22Z] R2robot but some people use whackadoodle versioning

message no. 177559

Posted by canton7 in #github at 2020-03-06T10:25:39Z

th_, it's a tricky question to answer: a repo might be highly compressed (for efficiently transfer it over a network), or it might have removed compression in lots of places (to let you switch branches quicker without having to decompress stuff), or it might have garbage in it (because running the GC is costly). Probably the best thing is to clone
+ [2020-03-07T04:31:35Z] very_sneaky hi all, is there a way to have a file named something other than README.md display automatically when navigating to a repo?
+ [2020-03-07T04:32:07Z] very_sneaky like, the_name_of_a_blog_article.md, for example
+ [2020-03-07T11:37:44Z] nedbat very_sneaky: tell us more about why you would want that file displayed instead
+ [2020-03-07T11:56:29Z] very_sneaky nedbat: i'm trying to implement a CI/CD pipeline for my blog posts, and so atm I have a repository for each post. I'd prefer to be able to name the content something with more semantic meaning than README.md
+ [2020-03-07T11:57:17Z] nedbat very_sneaky: a repo per post sounds like overkill.