4 ms·
This is one of the reasons that keeping code in a repository (especially a git repo) with good discipline on tying changes to issue descriptions is so key. It w
by shadowgovt 5y ago
This is one of the reasons that keeping code in a repository (especially a git repo) with good discipline on tying changes to issue descriptions is so key. It won't guarantee you'll find all relevant consequences of a change, but it really gives you a leg-up on the alternative of parsing out the results of a change by examining the code entrails.