Wil Thomason

We run the `fetch` command, which has a non-shallow depth specified by default, when a branch, tag, or commit has been set. Perhaps we can be smarter about only running...

@smhc: First off, I'm sorry for missing your PR for so long! I was too busy for `packer` for a while, and it looks to have come in during that...

Also @EdenEast do you mind fixing the conflicts before I review?

@smhc: Ok, thanks. I need to read through both PRs in detail. I will note that I do not favor having *both* lockfiles and snapshots (as mentioned on #1009); a...

Tagging @akinsho, @EdenEast, anyone else interested in contributing to the rewrite.

Oh, brilliant! That looks quite useful. Separately, more annotations is also a great way to start - that's a stated goal of the rewrite and will make working with the...

Right now, `packer` doesn't differentiate between install and update hooks - `run` executes for both events. If you'd like finer-grained control, this would be pretty easy to add, and I'm...

Thanks for the report. Can you isolate a commit in `packer` or your config files, etc. after which the problem started? This will help us isolate the problem.

Did you make changes to your config around this time? The line in the error message has to do with resolving `wants` and `after` - those features haven't been touched...

Hmm. Might be a long-standing bug, then. If either of you can isolate a minimal reproducing example, that would be really helpful.