latest 20 messages by nico103

+ [2020-07-13T04:11:39Z] nico103 appveyor works though
+ [2020-07-13T04:09:29Z] nico103 idk what changed
+ [2020-07-13T04:09:25Z] nico103 they used to appear, but now they don't
+ [2020-07-13T04:09:17Z] nico103 I've a repo with travis-ci, and PRs get built by travis as intended, but the travis builds don't appear in the checks list in each PR
+ [2017-03-03T22:19:19Z] nico103 oops, wrong channel
+ [2017-03-03T22:18:55Z] nico103 I've a repo whose builds are created but never kicked off
+ [2016-11-10T20:53:13Z] nico103 ah, the invites to repos don't show up like invites to orgs
+ [2016-11-10T19:40:33Z] nico103 what gives
+ [2016-11-10T19:40:25Z] nico103 but I never got the repo invites, even when resent
+ [2016-11-10T19:40:16Z] nico103 then I got invited to the org and that worked
+ [2016-11-10T19:40:04Z] nico103 I got invited to repos but not the org
+ [2016-11-10T19:39:55Z] nico103 is there a known bug with not receiving repo invitations?
+ [2015-08-10T15:25:25Z] nico103 CorySimmons: merge commits record that a merge happened (and where from), but they carry no content, so if you want to revert a merge you have to revert all the associated commits
+ [2015-08-09T23:56:54Z] nico103 scroll up today's #github log; I asked similar questions earlier
+ [2015-08-09T23:55:51Z] nico103 my approach is likely to be this: first include author/signer pubkeys in the main repo, then make the release, including a signature of it, and finally, include a file in the main repo that includes the hashes of all the released artifacts
+ [2015-08-09T23:54:53Z] nico103 Caelum: near as I can tell, no. github could use some features to make release signing easier
+ [2015-08-09T20:23:51Z] nico103 Still, I'd like to be able to refer to https://github.com/USER/REPO/releases/<commit-hash>/<artifact>