Every time we make a change to fetch, we have to make the same or similar change in secure-pull. As they get more labyrinthine, it is difficult to ensure they have all the same features / bug fixes. I imagine we wrote it this way so that one could have the pull command without also having the fetch command in their path, but we don't put this constraint on merge-pr or promote. Is there any reason we can't just use the one in the other, as we do for merge-pr and promote?
Every time we make a change to fetch, we have to make the same or similar change in
secure-pull. As they get more labyrinthine, it is difficult to ensure they have all the same features / bug fixes. I imagine we wrote it this way so that one could have thepullcommand without also having thefetchcommand in their path, but we don't put this constraint onmerge-prorpromote. Is there any reason we can't just use the one in the other, as we do formerge-prandpromote?