Question 400
A new Git branch tracks the wrong remote and pull requests are appearing against an unrelated repository. What should the engineer verify before declaring success?
Explanation
Correct Answer
This outcome directly verifies the scenario's required behavior: correct remote and base settings prevent code promotion to an unintended project.
Incorrect Answers
Embedding secrets is not a safe fix for repository misconfiguration.
Branch names do not change which remote is tracked.
Correct code in the wrong repository violates deployment provenance.