Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can secure-pull use secure-fetch instead of repeating the entire script? #53

Open
gchronis opened this issue Oct 26, 2017 · 0 comments
Open

Comments

@gchronis
Copy link
Contributor

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant