+ [2020-06-19T22:58:45Z] jhass but they provide no place to host any artifacts
+ [2020-06-19T23:11:05Z] dreisner jhass: huh. talking to the alarm folks sounds like a way better idea. i'm friendly with kevin
+ [2020-06-19T23:11:15Z] dreisner had no idea this was a thing they did
+ [2020-06-19T23:11:29Z] jhass I mean I never did any such
+ [2020-06-19T23:11:38Z] jhass but I figured it wouldn't hurt to ask

message no. 182563

Posted by famubu in #github at 2020-06-19T16:58:00Z

And would both licenses be mentioned in the repo (MIT and LGPL) then? Only the maintainer contributed during the GPL period.
+ [2020-06-20T00:16:50Z] Abhishek09 hi everyone, i have 1 query about release asstets of github
+ [2020-06-20T00:29:31Z] R2robot You can just ask... if someone knows, they'll answer.
+ [2020-06-20T00:37:10Z] Abhishek09 i have to create a github release by making python script to atomate the requirement.txt file from whl files directory. Any idea?
+ [2020-06-20T18:07:05Z] shakeelshahzac Hi, is there a way to know from a commit if it was merged with "Create a Merge Commit", "Squash and Merge" or "Rebase and Merge" option?
+ [2020-06-21T01:37:21Z] sm[m] g'day all. I made a github release with a signed tag named 1.18. I forgot I use that naming for release branches, so I'd like to rename the tag to r1.18. Would you know if I can do this, without messing up the github release ?