Option to --unshallow before committing

[rhys-vdw]

Firstly, loving the tool, thanks :-)

I'd like an option to unshallow a repo before merging.

Workflow in question

If we remove the fetch-depth: 0 here we get a shallow checkout (which is desirable, this repo is >3GB), but the downside is that we can't merge back into master due to:

fatal: refusing to merge unrelated histories

So, the ideal behaviour here is:

1. Check out shallow.
2. Make any changes
3. if there are changes
   1. do a git fetch --unshallow
   2. then merge

So I could add a dirty check and unshallow as a different step. But, because git-auto-commit-action handles the dirty check, it would be very convenient to have an option like:

      - name: Push updated submodule
        uses: stefanzweifel/git-auto-commit-action@v5
        with:
          file_pattern: recoil-lua-library
          unshallow: true
          commit_message: |
            Update Lua libary submodule

[stefanzweifel]

Thanks for the suggestion.

In v5, we do a git-fetch, but in the unreleased v6 this feature will be removed. This wouldn't solve your problem, right?

As you still need to make a git fetch --unshallow.
I'm hesitant to add it back, as it led to other issues. Have to think about this.

Maybe I can add some sort of hooks, so consumer of the action can execute their own code "before a commit" is being made or "before a tag" is created.

[rhys-vdw]

I have realized that because we do a partial clone (of a tiny folder) it's actually not at all a problem for this workflow, so def take it as a suggestion and nothing more!

[rhys-vdw]

Fwiw a hook does sound pretty good, but I guess at some stage it might just make more sense for me to break it into two actions, one that checks for uncommited changes, and another that commits with a skip if nothing to commit.