You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One idea would be to blow up only if it's been merged to master. This is sneaky and evil from a CI perspective but could be one way to detect something you want to remove after a feature branch is merged but the dates aren't clear/meaningful.
I presume we'd do this by shelling out to git b/c lazy
The text was updated successfully, but these errors were encountered:
I think I'd rather prefer to use the proposed if predicate (or wrapping in a vanilla conditional) where the condition checks for "evidence of the PR being merged".
ie, if the feature PR adds a new method to an object, I'd rather write a todo on master that blows up if the desired method exists.
(I assume this is in cases where the PR in question couldn't take care of the todo item itself...)
One idea would be to blow up only if it's been merged to master. This is sneaky and evil from a CI perspective but could be one way to detect something you want to remove after a feature branch is merged but the dates aren't clear/meaningful.
I presume we'd do this by shelling out to git b/c lazy
The text was updated successfully, but these errors were encountered: