I like the -f option but it deletes all the remote branches without asking. It would be great to have some whitelisting so I could keep the production branch but still use the -f option.

git checkout -b something
git checkout master
git fresh
git checkout -

Unfortunately this will stay in the master instead of the something branch.

Not sure if its isolated to me or now but i fresh no longer removes branches when i run it

running g fresh -f nets me

Fetching origin
Pruning origin
URL: https://github.com/wheniwork/{repo}
 * [pruned] origin/feature/update-deps
 * [pruned] origin/fix/fix-case
 * [pruned] origin/fix/fix-jenkins
Already on 'master'
Your branch is up-to-date with 'origin/master'.

when the following marked branches are merged.

g branch --list
  feature/add-devtool-docs < merged
  feature/add-pull-approve < merged
  feature/add-uploader-analytics
  feature/add-webpack-dashboard < merged
  feature/analytics-mk1 < merged
  feature/billing-react
  feature/de-ify-dependancies
  feature/invite-coworker
  feature/pending-coworkers
  feature/update-deps < merged
  feature/workchat-firebase-poc
  fix/correct-readme < merged
  fix/fix-case < merged
  fix/fix-jenkins < merged
* master
  react

It would be really nice to have a dry run parameter, which outputs the changes that would be made.

Would be super nice if this were available through Homebrew

Hi!

We have a github protected branch that cannot be deleted.

I know I can add it to .freshignore but would be nice if the error were not the following but rather something more informative if possible:

git fresh -f
Fetching origin
[git-fresh] Error on line 258: fi

Cheers,
f

e.g. -S

[git-fresh] Local stale branches found: selenium-secondary-stateless
[git-fresh] Delete stale branches with: git fresh -f
Auto packing the repository in background for optimum performance.
See "git help gc" for manual housekeeping.
error: The last gc run reported the following. Please correct the root cause
and remove .git/gc.log.
Automatic cleanup will not be performed until the file is removed.

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

[git-fresh] Error on line 321: git gc --auto --prune=now

seems one fix here is to detect if there are too many unreachable objects, and run git prune before gc

Based on https://github.com/imsky/git-fresh/releases/latest it's not clear to me whether 1.3.0 or 1.10.0 is the current stable release version. Could you clarify which should be in Homebrew now? Thanks!

-M resets local root to match remote root
-W wipes local workspace

Given I run git fresh -f from a branch that has been merged it can leave untracked files in the working tree in some cases if they were deleted on the master branch in between the local version of master git fresh -f will sync and the yet to be synced remote version. This causes me to have to rm the untracked files afterwards which is easy to forget and might be swept up into a commit by an unsuspecting git noob.

bad remotes can cause git pull to fail, which leaves the repo in an non-git-freshable state

I love git fresh. I use it constantly, but the only way I notice flags that I don't use already is by looking at this repo directly. It would be amazing if there was a man page for it so that git help fresh or git fresh --help worked.

When running git fresh -f, I always get this error:

[git-fresh] Error on line 173: echo -n $LOCAL_STALE | tr " " "\0" | xargs -0 git branch -d 2> /dev/null

According to brew upgrade git-fresh, I'm using version 1.6.2.

also document .freshignore

I don't see in the source anywhere that you are handling git sub-modules. On some of my repos I need to pull and then run:

git submodule update --init --recursive

It would be great if you could do this as well.

It would be nice to be able to remove stale branches, but only the local ones. My use case is I'm working in a large team, and there are a bunch of branches that while stale upstream, are not necessarily ones we want to remove without a discussion.

if the user is in a directory on a branch that doesn't exist on master, they'll get a "no such file or directory" error while getting current working directory in the script.

the way this could work is:

• detect repo root
• save current dir
• change dir to repo root
• run fresh operations
• change dir to previous current dir (if it exists)

sometimes the HEAD ref goes missing, maybe it's possible to restore it