< kallewoof> BlueMatt: belated response, but lol! I didn't really expect us to go that route, but still. Someone from AntPool apparently said it was a misconfiguration, fwiw.
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/8a503a6c6dd4...6899ef3f0e0c
< bitcoin-git> bitcoin/master c061be1 practicalswift: tests: Mark unit test blockfilter_index_initial_sync as non-deterministic
< bitcoin-git> bitcoin/master 6899ef3 MarcoFalke: Merge #16143: tests: Mark unit test blockfilter_index_initial_sync as non-...
< bitcoin-git> [bitcoin] MarcoFalke merged pull request #16143: tests: Mark unit test blockfilter_index_initial_sync as non-deterministic (master...non-determinism-in-blockfilter_index_initial_sync) https://github.com/bitcoin/bitcoin/pull/16143
< bitcoin-git> [bitcoin] Empact opened pull request #16186: doc/lint: Fix spelling errors identified by codespell 1.15.0 (master...codespell-errors) https://github.com/bitcoin/bitcoin/pull/16186
< bitcoin-git> [bitcoin] emilengler opened pull request #16187: RPC: Add aliases for priv and pub rpc calls (master...master) https://github.com/bitcoin/bitcoin/pull/16187
< BlueMatt> kallewoof: I figured, thanks for following up
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #16187: RPC: Add aliases for priv and pub rpc calls (master...master) https://github.com/bitcoin/bitcoin/pull/16187
< bitcoin-git> [bitcoin] MarcoFalke opened pull request #16188: net: Document what happens to getdata of unknonw type (master...1906-netGetData) https://github.com/bitcoin/bitcoin/pull/16188
< dongcarl> Review beg for #16184, gitian builds are failing again...
< gribble> https://github.com/bitcoin/bitcoin/issues/16184 | scripted-diff: gitian: Use REFERENCE_DATETIME directly. by dongcarl · Pull Request #16184 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] MarcoFalke opened pull request #16189: 0.18: Backport "Add -ignorepartialspends to list of ignored wallet options" (0.18...1906-18Backport) https://github.com/bitcoin/bitcoin/pull/16189
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/6899ef3f0e0c...473c6b7c5ab0
< bitcoin-git> bitcoin/master 993aa41 Carl Dong: scripted-diff: gitian: Use REFERENCE_DATETIME directly.
< bitcoin-git> bitcoin/master 473c6b7 MarcoFalke: Merge #16184: scripted-diff: gitian: Use REFERENCE_DATETIME directly.
< bitcoin-git> [bitcoin] MarcoFalke merged pull request #16184: scripted-diff: gitian: Use REFERENCE_DATETIME directly. (master...2019-06-fix-tar-mtime) https://github.com/bitcoin/bitcoin/pull/16184
< jnewbery> pierre_rochard: the PRs themselves have 'events' for when they're added or removed from projects, eg: https://github.com/bitcoin/bitcoin/pull/15141#event-2066722988 . Are you able to access those through the API for your analytics?
< bitcoin-git> [bitcoin] alexjumaev opened pull request #16190: Merge pull request #1 from bitcoin/master (master...master) https://github.com/bitcoin/bitcoin/pull/16190
< bitcoin-git> [bitcoin] alexjumaev closed pull request #16190: Merge pull request #1 from bitcoin/master (master...master) https://github.com/bitcoin/bitcoin/pull/16190
< pierre_rochard> jnewbery: thanks for the suggestion! I see it in the docs, looks like a slam dunk! https://developer.github.com/v4/object/removedfromprojectevent/