refs: add list subcommand #1
Open
Conversation
This file contains hidden or 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
consolidate `git show-ref` command as `git refs list` along with some of
the flags. Namely:
- --branches | --heads(deprecated)
- --head
- --tags
So, now new subcommands can replace old ones like:
- `git show-ref [--head]` -> `git refs list [--head]`
- `git show-ref [--branches | --heads]` -> `git refs list [-branches | --heads]`
- `git show-ref [--tags]` -> `git refs list [--tags]`
Also add tests for this subcommand along with their flags.
Signed-off-by: Meet Soni <[email protected]>
inosmeet
force-pushed
the
preview-refs-list
branch
from
9cb45bf to
2473804
Compare
inosmeet
pushed a commit
that referenced
this pull request
Jun 4, 2025
Signed-off-by: Junio C Hamano <[email protected]>
inosmeet
pushed a commit
that referenced
this pull request
Jun 4, 2025
The GitHub's CI workflow uses 'actions/checkout@v4' to checkout the repository. This action defaults to using the GitHub REST API to obtain the repository if the `git` executable isn't available. The step to build Git in the GitHub workflow can be summarized as: ... - uses: actions/checkout@v4 #1 - run: ci/install-dependencies.sh #2 ... - run: sudo --preserve-env --set-home --user=builder ci/run-build-and-tests.sh #3 ... Step #1, clones the repository, since the `git` executable isn't present at this step, it uses GitHub's REST API to obtain a tar of the repository. Step #2, installs all dependencies, which includes the `git` executable. Step #3, sets up the build, which includes setting up meson in the meson job. At this point the `git` executable is present. This means while the `git` executable is present, the repository doesn't contain the '.git' folder. To keep both the CI's (GitLab and GitHub) behavior consistent and to ensure that the build is performed on a real-world scenario, install `git` before the repository is checked out. This ensures that 'actions/checkout@v4' will clone the repository instead of using a tarball. We also update the package cache while installing `git`, this is because some distros will fail to locate the package without updating the cache. Helped-by: Phillip Wood <[email protected]> Signed-off-by: Karthik Nayak <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
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.
consolidate
git show-refcommand asgit refs listalong with some of the flags. Namely:- --branches | --heads(deprecated)
- --head
- --tags
So, now new subcommands can replace old ones like:
git show-ref [--head]->git refs list [--head]git show-ref [--branches | --heads]->git refs list [-branches | --heads]git show-ref [--tags]->git refs list [--tags]Also add tests for this subcommand along with their flags.