Cody

[Cody @XT3000]

@GHchangelog Looks like the "not planned" icon is not used when referencing issues in a list 😭

[Cody @XT3000]

@TrueAndre_601 @GHchangelog https://t.co/Vc51M2xNCo 🥰

[Cody @XT3000]

@GHchangelog The first "here" link is broken (missing a colon?). https://t.co/E6oMJa8pdL

[Cody @XT3000]

@GHchangelog Seems to include changing the base branch midway, awesome!

[Cody @XT3000]

@t3n SMEs sollte wohl eher als "Fachkräfte" (subject-matter experts) übersetzt werden statt als "kleine und mittelständische Unternehmen" (KMU)? 🙂 https://t.co/5nvn7HvO6h

[Cody @XT3000]

@GHchangelog The irony of the screenshot showing a comment at the end of a line, marked as invalid, while also talking about the syntax enhancement that allows you to have comments like this 😄

[Cody @XT3000]

@GHchangelog A small step for @github, a giant leap for designer kind.

[Cody @XT3000]

@Bumi @peter_szilagyi @LeahNeukirchen @travisci What not to do when using pull_request_target: https://t.co/IZjGPcHVG7

[Cody @XT3000]

@Bumi @peter_szilagyi @LeahNeukirchen @travisci GitHub Actions doesn't give forks access to secrets except for the pull_request_target trigger. But that will use the workflow of the base branch. So you can't access secrets AND modify the workflow to leak them. Unless your workflow explicitly checks out the head branch (unsafe)

[Cody @XT3000]

@Bumi @peter_szilagyi @LeahNeukirchen @travisci Using SHA commit hashes for Actions: https://t.co/NgvobDrEJk

[Cody @XT3000]

@Bumi @peter_szilagyi @LeahNeukirchen @travisci The default GITHUB_TOKEN is accessible for forks, but has read permissions only. A bigger risk are third-party Actions that could steal your secrets. Better review their code and pin the version using the full commit hash. About GITHUB_TOKEN: https://t.co/YZjlk5DPRI

[Cody @XT3000]

@github FYI: The "send us your feedback" at the end of the blog post is broken.

[Cody @XT3000]

What does pfp stand for?

[Cody @XT3000]

@cyberlypse @MaterialIcons All codepoints were reassigned in v5.0 to exclusively use the private use area. Previous versions used assigned codepoints for some icons, i.e. there were conflicts.

[Cody @XT3000]

@leMaikOfficial @MaterialIcons There is a release every ~100 icons, hence every 10th is a major version for breaking changes. v5.0 is a bit different: 5045-4995 (v4.9.95) = 50 new icons (but a lot of changes), leaving more wiggle room for future releases regarding the icon count / version number.

[Arango @arangoai]

#InsideArangoDB our team is hard at work in #Barcelona for the #ArangoDB 2020 Gathering ✨🥑

[Cody @XT3000]

@templarian @PeterAG1989 Was Austin sagt. Die Community Icons stehen unter SIL/MIT-Lizenz und ich stehe voll hinter dem Projekt und Libre/Open Source - du kannst meine Icons gerne verwenden. Das Basisicon ist übrigens ebenfalls ein Community Icon. 👍 Aber danke fürs fragen!

[Arango @arangoai]

"Hi 2020"
"Hi ArangoDB 3.6! How are you?"
"Feeling 30x faster!"

New release packed with performance improvements, highly available & transactional deployment mode as well as ArangoSearch Upgrades
👉https://t.co/3FumUR5PEv

#ArangoDB #NoSQL #Performance #HighAvailability

[Cody @XT3000]

@Una @argyleink You mentioned CSS regions (https://t.co/dmqytmUpV9) but the Chromium status is "No longer pursuing" since 2014. Not much activity in the csswg-drafts repo to improve the specs either. I'm confused 🥺 Would ♥ to see more features for paged media being added to the web platform.

[Cody @XT3000]

@templarian @MaterialIcons Your miso soup addiction? 😋