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

Allow --no-single-branch git option (dupe of #4806) #9868

Open
drd opened this issue Jul 11, 2018 · 2 comments
Open

Allow --no-single-branch git option (dupe of #4806) #9868

drd opened this issue Jul 11, 2018 · 2 comments

Comments

@drd
Copy link

drd commented Jul 11, 2018

Overview

It is useful to be able to compare across branches for certain CI-related tasks. With current versions of git, cloning using the --depth flag also automatically enables the --single-branch option, causing git to fetch only the specified branch for the commit travis is building. As pointed out in #4806, there are ways around this, but they have a significant performance penalty: running git fetch --unshallow retrieves the entire commit history, which for many projects, is an undue burden.

Request

Please allow an option to specify --no-single-branch in the travis config. 🙏

@stale
Copy link

stale bot commented Oct 9, 2018

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue in 7 days. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please respond before the issue is closed, or open a new one after. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues

@widyhafiz03
Copy link

Good job, good first issue

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

No branches or pull requests

4 participants
@drd @BanzaiMan @widyhafiz03 and others