Set --depth on git-fetch and make call to git-fetch optional #131
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This new option will allow users to skip the execution of `git fetch` if it has a negative impact in their workflows. In a future PR I will probably remove the call to git-fetch interely. It was added in #108 in relation to a problem with slashes in branch names. That problem wasn't properly fixed though.
This was referenced Mar 11, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this PR we're adding a new
skip_fetchinput option to disable the call togit-fetch. As reported in #130, callinggit-fetchcan have a negative impact on the performance of the Action in huge git repositories.In addition, we added the
--depthargument togit-fetchto not fetch the entire history of the repo, but only the last 3 commits.Sidenote: The call to
git-fetchhas been added in #108 in relation to a problem reported in #106 with branch names likerefactor/name. The/previously created problems.By calling
git fetchwe've seemed to fix the error 🤷 Now that we have a test suite, it would probably make sense to switch to the proposed solution of usinggit switch(Will work on this in a separate PR)