+[9 years ago]ThiefMasteralso, your pk should be in ~/.ssh/ which is outside your repo +[9 years ago]malluHas anyone use GHE web hooks with slack? +[9 years ago]toogleyThiefMaster: well, i've recently read a post in which a "ext:[...] PRIVATE KEY" (but i forgot the exact extension) listed about 5000 files with uploaded private keys. that made me fear to do accidently the same thing +[9 years ago]TobbiWhere can I see the commits to master since a certain release? +[9 years ago]TobbiIn github, I mean.
message no. 120823
Posted by apaze in #github at 2015-11-20T14:57:45Z
I don't understand as my previous build went well at the cloning step :/
+[9 years ago]criticalcatSuppose I forked an upstream repo, committed a couple of changes to my/master, created a pull request to integrate my/master to upstream/master, further changes were made on upstream/master, I merged upstream/master into my/master (not realizing that this merge would show up on the PR, that I should have branched to make the change), closed the PR, and want to clean up my/master. Locally it looks better after creating a branch +[9 years ago]criticalcatmy/masterundo from the crappy master and creating a branch my/smallchange branch, and doing "git branch -f master HEAD~24" to put my/master back the way it was before I started mucking around. Question: what will happen to the (closed) PR that was suggesting a merge from my/master to upstream/master when my/master's about to be overwritten? +[9 years ago]criticalcatguess I will find out when I force push +[9 years ago]criticalcat: D +[9 years ago]animalroamhello, I am new to github and would like to use it with someone to create a website