timrogers

I wonder how this works under the hood and if it is significantly compromises security - no technical details in the article

It’s an incredible map - so many fun memories!

Tim from the Copilot coding agent team here. We've now disabled these tips in pull requests created by or touched by Copilot, so you won't see this happen again for future PRs.

We've been including product tips in PRs created by Copilot coding agent. The goal was to help developers learn new ways to use the agent in their workflow. But hearing the feedback here, and on reflection, this was the wrong judgement call. We won't do something like this again.

> Reviewing AI output all day without the dopamine of creation is not a sustainable job description.

I agree that reducing engineers’ careers to code review will lead to burnout (amongst other problems).

But I think the reason we’re headed in this direction is precisely because creating with AI /can/ deliver “the dopamine of creation”.

It doesn’t deliver that hit for everyone - but it does for the half of engineers who are more excited about building new things than the act of coding.

Teams build more and ship faster because it’s so much easier to do that with AI - and it’s fun - and that leads to increased review load.

That would be the normal pattern. But you could certainly stop after the LLM picks the tool and provides the arguments, and not present the result back to the model.

The claim in the quote here is simply not true.

The travel agency is the one that collects your personal information - but it (unsurprisingly) immediately passes just about everything to the airline: name, date of birthday, phone number, email etc.

In general, the airline won’t get your payment details though.

GitHub PM here. We have tried this, but we weren't able to get results that we were satisfied with. Of course, you have to revisit these things regularly, as the models and wider state of the art are evolving so quickly!

Tim from the GitHub Copilot coding agent product team here!

@artdigital is on the money here. Our quick tip for beginners is to use `copilot-instructions.md` (which we can now generate for you <3), but for more serious use, we'd strongly recommend adding `copilot-setup-steps.yml`.

That gets you a deterministic setup - and for many teams, it'll be easy, as you can just copy and paste from existing Actions workflows.

Interestingly, the title refers to citizens but the body only refers to residents:

> the AWS European Sovereign Cloud is operated only by personnel who are European Union (EU) residents located in the EU, subject to EU law.

The #5 contributor thing is a stat from a single repository where we’re building Copilot coding agent.

Humans are indeed in slots #1-4.

After hearing feedback from the community, we’re planning to share more on the GitHub Blog about how we’re using Copilot coding agent at GitHub. Watch this space!

At the moment, we're using Claude 3.7 Sonnet - but we're keeping our options open to experiment with other models and potentially bring in a model picker.

(Source: I'm on the product team for Copilot coding agent.)