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
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?
The text was updated successfully, but these errors were encountered:
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 thepull
command without also having thefetch
command in their path, but we don't put this constraint onmerge-pr
orpromote
. Is there any reason we can't just use the one in the other, as we do formerge-pr
andpromote
?The text was updated successfully, but these errors were encountered: