Good reminder to go into every change and annotate (planned, built, or verified) a story key somewhere in the code. Having the branch name or commit description mention the key would make it easier too.
the annotation is the easy part. The hard part is knowing whether REQ-123 is still satisfied after 67 subsequent commits touch that file. git blame can't tell you that. You need something that scans the current working tree and rebuilds the trace on every change. (That's what RTMify does)
2 comments
[ 3.2 ms ] story [ 10.9 ms ] thread