featured in #376
Experiment: The Hidden Costs Of Waiting On Slow Build Times
- Natalie Somersall tl;dr: Senior Solutions Engineer at GitHub conducted an experiment to understand tradeoffs between productivity and hardware. "When you ask a developer whether they’d prefer more or less powerful hardware, the answer is almost always more powerful hardware. More powerful hardware means less time waiting on builds - and that means more time to build the next feature or fix a bug. But even if the upfront cost is higher for higher-powered hardware, what’s the actual cost when you consider the impact on productivity?"featured in #374
Everything New From GitHub Universe 2022
- Thomas Dohmke tl;dr: "AI will soon be integrated into every aspect of the developer experience, and, therefore, we’re making GitHub Copilot even more accessible. Coming soon, businesses can purchase and manage seat licenses for GitHub Copilot for their employees."featured in #367
8 Things You Didn’t Know You Could Do With GitHub Copilot
- Rizel Scarlett tl;dr: (1) Assisting non-native English speakers. (2) Creating dictionaries with lookup data. (3) Matching patterns with regular expressions. (5) Preparing for technical interviews. (6) Sending tweets. (7) Exiting Vim. (8) Navigating a new codebase with Copilot Labs.featured in #352
Research: Quantifying GitHub Copilot’s Impact On Developer Productivity And Happiness
- Eirini Kalliamvakou tl;dr: Research by GitHub on Copilot found: (1) Developers reported that Copilot helped them stay in the flow (73%) and preserve mental effort during repetitive tasks (87%). (2) The group that used GitHub Copilot had a higher rate of completing the task - 78%, compared to 70% in the group without Copilot.featured in #351
Automate Pull Request Labels Based On Changed Files With Actions
- Lloyd Atkinson tl;dr: "That’s a lot of functionality that can be built with labels. As an example, I’ll show how to add labels automatically depending on which area of a codebase has changed. This is what I use in every project I work on as it allows maintainers oversight and awareness of the impacts of changes. It does not depend on the language or types of files - it’s based on the git diff and paths."featured in #340
An Experiment To Test GitHub Copilot's Legality
- Rohan Kumar tl;dr: "This post is satirical commentary on: (1) The absurdity of Microsoft and OpenAI’s legal justification for GitHub Copilot. (2) The oversimplifications people use to argue against GitHub Copilot. (3) The relationship between capital and legal outcomes. (4) How civil cases seem like sporting events where people “win” or “lose”, rather than opportunities to improve our understanding of law."featured in #331
Best Practices To Keep Your Projects Secure On GitHub
- Justin Hutchings tl;dr: "With Dependabot, not only can you catch vulnerable dependencies, but you can fix them as well. It automatically checks your dependency files for outdated requirements and opens individual pull requests for any it finds. It then notifies you and suggests fixes."featured in #315
How To Use Github Copilot With Swift Using Visual Studio Code?
- An Tran tl;dr: "Personally, I believe Github Copilot could potentially become a very helpful tool to generate code using API that developers are not familiar with, or common snippets that are popular enough to be generated automatically."featured in #267
GitHub CLI 2.0 Includes Extensions!
- Billy Griffin tl;dr: "Creating extensions is simple. Each extension is just a repository prefixed with gh-, and you can easily define the extension. We even built tooling into GitHub CLI itself to allow you to get started more quickly with gh extension create, which creates a scaffolded repository for you with some pre-written Bash that will help you get started."featured in #248