Comment 1 for bug 1676243

This for me actually causes the `go` part to be fetched and go through the lifecycle. However, removing the `after` keyword completely does skip everything, which means it indeed isn't included in the dirty calculation.