+ [2020-06-19T23:11:38Z] jhass but I figured it wouldn't hurt to ask
+ [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?

message no. 182611

Posted by shakeelshahzac in #github at 2020-06-20T18:07:05Z

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 ?
+ [2020-06-21T08:36:20Z] jhass sm[m]: it will need to be a new github release
+ [2020-06-21T08:36:52Z] jhass pretty sure it's linked by name to the tag
+ [2020-06-21T10:23:17Z] famubu I have a branch which was merged to master. After while I noticed a bug in it and fixed it. Should I commit to the same branch (with which the original PR was made) or should I make a new PR?
+ [2020-06-21T10:38:57Z] jhass I'd do a new one but it really doesn't matter. Either way the original PR won't reopen but you can make a new one from the old branch too