-
-
Notifications
You must be signed in to change notification settings - Fork 926
Comparing changes
Open a pull request
base repository: gitpython-developers/GitPython
base: 3.1.38
head repository: gitpython-developers/GitPython
compare: 3.1.40
- 6 commits
- 6 files changed
- 2 contributors
Commits on Oct 18, 2023
-
Add missing info in Submodule.remove docstring
This rewords and adds some missing information to the docstring of Submodule.remove, for the "method" parameter, discussed in #1712. It uses the second suggestion presented in that issue, formatted in the style of the surrounding docstring (an 88-column wrap). It also does some other rewording in that docstring, for clarity, at the end of that same section (on the "method" parameter), and a small punctuation fix in the section about the "force" parameter.
Configuration menu - View commit details
-
Copy full SHA for 427c177 - Browse repository at this point
Copy the full SHA 427c177View commit details -
Don't pre-clone submodules on CI, at least for now
This has actions/checkout no longer automatically clone submodules in the CI test workflows. This change is for the purpose of reproducing #1713, to allow the forthcoming fix for it to be tested. However, continuing to rely on init-tests-after-clone.sh to get the submodules would serve as a kind of regression testing for #1713. So it is unclear at this time if and when this change should be undone.
Configuration menu - View commit details
-
Copy full SHA for bb48c87 - Browse repository at this point
Copy the full SHA bb48c87View commit details -
Have init script clone submodules unconditionally
Since 7110bf8 (in #1693), "git submodule update --init --recursive" was not run on CI, on the mistaken grounds that the CI test workflows would already have taken care of cloning all submodules (ever since 4eef3ec when the "submodules: recursive" option was added to the actions/checkout step). This changes the init-tests-after-clone.sh script to again run that command unconditionally, including on CI. The assumption that it wasn't needed on CI was based on the specific content of GitPython's own GitHub Actions workflows. But this disregarded that the test suite is run on CI for *other* projects: specifically, for downstream projects that package GitPython (#1713). This also brings back the comment from fc96980 that says more about how the tests rely on submodules being present (specifically, that they need a submodule with a submodule). However, that is not specifically related to the bug being fixed.
Configuration menu - View commit details
-
Copy full SHA for 8ea3133 - Browse repository at this point
Copy the full SHA 8ea3133View commit details -
Merge pull request #1714 from EliahKagan/docstring-submodule-remove
Add missing info in Submodule.remove docstring
Configuration menu - View commit details
-
Copy full SHA for a5b2fa5 - Browse repository at this point
Copy the full SHA a5b2fa5View commit details -
Merge pull request #1715 from EliahKagan/ci-submodules
Have init script clone submodules unconditionally
Configuration menu - View commit details
-
Copy full SHA for 5ba2b84 - Browse repository at this point
Copy the full SHA 5ba2b84View commit details -
Configuration menu - View commit details
-
Copy full SHA for 44102f3 - Browse repository at this point
Copy the full SHA 44102f3View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 3.1.38...3.1.40