Загрузка видео...
Не удалось загрузить видео
No tech background? You can still use GitHub Copilot CLI to help build the tools you need. Victoria, an operations manager on the GitHub legal team, needed a centralized platform for operational tools. Instead of using engineering resources, she used Copilot CLI to build the Innovation Marketplace herself. ✨... show more
68,194 просмотров • 1 день назад •via X (Twitter)
Комментарии: 15
More Copilot CLI use cases from the GitHub legal team 👇
❤️❤️❤️
No customer support background? Join GitHub, they hiring.
the killer step is making the generated tool handoffable: repo, tests, owner, rollback. then engineering can inherit a working system instead of rebuilding a demo.
This is pretty neat
No dev team? Copilot's your new BFF, fr.
The leverage is organizational, not just technical—domain experts can turn bottlenecks into tools without waiting in the engineering queue.
Wtf, so anyone can be a dev now? LMAO
The real unlock is giving domain experts a build button: fewer tickets to engineering, more tools shaped by the people using them.
The story is interesting, but the handoff still matters. What did Copilot generate versus what needed review before this became a shared tool?
Who needs a technical background when you have a PhD in coffee-fueled problem-solving? 🙌💻
Hi team, could you help route Ticket #4713787 to Trust & Safety? Account urzeye was mistakenly flagged by automated abuse detection. Requested details provided 10+ days ago. Our public repo urzeye/ophel returns 404 to active users. Thanks!
This is a great example of AI lowering the barrier to building useful tools. Non-engineers can ship much more now.
the useful shift is people building their own internal software instead of filing another ticket. the interface is becoming the disposable part
That’s a pretty meaningful shift champ
