Preventing bad patterns
A new developer has joined the ShelfLife team. In one of their first pull requests, you've spotted hardcoded API keys in the source code. You've flagged and fixed the issue, but the pattern may keep coming back.
What's the most effective way to prevent hardcoded credentials from appearing in future code that Copilot suggests?
This exercise is part of the course
Software Development with GitHub Copilot
Hands-on interactive exercise
Turn theory into action with one of our interactive exercises
Start Exercise