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

Use --prune for all git fetch operations #650

Merged
merged 1 commit into from
Feb 20, 2019

Conversation

dliappis
Copy link
Contributor

In environments with long lived git checkouts git fetch operations can
fail after time, due to rebasing operations or other reasons with
messages like:

There are too many unreachable loose objects; run 'git prune' to
remove them.

Ensure git fetch always uses the --prune flag.

In environments with long lived git checkouts git fetch operations can
fail after time, due to rebasing operations or other reasons with
messages like:

```
There are too many unreachable loose objects; run 'git prune' to
remove them.
```

Ensure `git fetch` always uses the --prune flag.
@dliappis dliappis added this to the 1.0.4 milestone Feb 20, 2019
@dliappis dliappis added enhancement Improves the status quo :misc Changes that don't affect users directly: linter fixes, test improvements, etc. labels Feb 20, 2019
Copy link
Member

@danielmitterdorfer danielmitterdorfer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! LGTM

@dliappis dliappis merged commit 99e90d1 into elastic:master Feb 20, 2019
@dliappis dliappis deleted the prune-everywhere branch February 20, 2019 09:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improves the status quo :misc Changes that don't affect users directly: linter fixes, test improvements, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants