Add prune to submodule step
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 19
- Forks
- 18
- Avg merge
- 1d 53m
- Merged PRs (30d)
- 1
Description
Either git remote prune origin or git fetch --prune should be used so that if --shallow is removed from OMERO-push, the OMERO-build step will not fail on trying to checkout scripts.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the OMERO-push and OMERO-build steps in the repository and inspect how the submodule is fetched before scripts are checked out. Choose one of the proposed prune commands, then verify that removing --shallow from OMERO-push no longer causes OMERO-build to fail when checking out scripts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100