Dimitri Merejkowsky

> In all seriousness, I'm also wondering if the steps 1 to 6 should be a feature of git itself ? Maybe something with `git update-ref`?

Well, what you're proposing does not do step 3 and 5 (where we temporarily switch branches and back). But it works well with ` tsrc foreach -- git pull`

I'm confused. `tsrc sync` implementation only calls `git fetch` and `git merge --ff-only @{upstream}` - why would settings in `[rebase]`and `[pull]` be used ?

I prefer talking about the `sync.sh` in the doc rather than change tsrc's code. It's a *really* flexible method and you can put it under version control for your organization...

> It does not clone new repos added to the manifest since the last sync. It's very clearly a workaround, not a proper fix. Hum. I think you're right. Did...

> Has there been any discussion of supporting a --tag command-line option when initializing, permitting one to pull a tagged version of the manifest file? I don't think so. Do...

So ... I went ahead and try implementing 3/ but there's an issue. But `tsrc` is not like other tools. Currently, when we parse the manifest we put `master` in...

Nope. You can only use `{current_version}` and `{new_version}` in the hooks commands. There are several approaches we could take: 1/ Adapt the syntax. I think what you're proposing cannot work...

Some skeleton if you want to see what 3/ would like: ```python import sys import re new_version = sys.argv[1] regex = re.compile( .... # whatever regex is in tbump.toml re.VERBOSE,...

Looks nice. I think we need to implement breadth-first search for untracked git repository (a simple call to os.walk maybe too slow). Wanna try working on a PR ?