BartWullems's blog is a platform for sharing insights and expertise in Microsoft technologies, software development best practices, and programming tutorials. Through articles, code samples, and technical discussions, BartWullems offers insights into building scalable, maintainable, and performant software applications using Microsoft technologies such as .NET, Azure, and Visual Studio. Readers can learn about design patterns, development techniques, and tooling recommendations to enhance their skills and productivity as Microsoft developers. Additionally, BartWullems provides updates on the latest developments in Microsoft ecosystem, community events, and industry trends to help developers stay informed and engaged in the Microsoft developer community.

The Art of Simplicity

GitHub Copilot CLI supports hooks — shell scripts that run at specific lifecycle points during a session. Hooks receive structured JSON via stdin and can optionally return JSON to influence agent behavior. Key hook types include sessionStart, sessionEnd, and preToolUse, the last of which can allow, deny, or prompt for approval before any tool executes. A practical example shows blocking rm -rf commands via a preToolUse bash script. Important behaviors: hook failures don't block execution, multiple hooks of the same type run sequentially with any deny being sufficient to block, and timeouts default to 30 seconds. Hooks are stored in .github/hooks/*.json and are especially valuable for platform and DevOps teams enforcing org-wide security policies, audit logging, and access controls across Copilot CLI sessions.

GitHub Copilot CLI Tips & Tricks — Part 4: Automating and enforcing policies with hooks