-
-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] fetch HEAD without tags #220
Comments
Thanks for reporting this issue. |
Fetching tags would be due to specifying - uses: actions/checkout@v2
with:
fetch-depth: 0 See: https://github.com/actions/checkout#fetch-all-history-for-all-tags-and-branches You can optionally switch to - uses: actions/checkout@v2
with:
fetch-depth: 2 |
Actually I'm just using: - uses: actions/checkout@v2
- id: changed-files
uses: tj-actions/changed-files@v10.1
with:
files: \.md$ But the fetching of tags comes from this action, see the link I left above: https://github.com/tj-actions/changed-files/blob/main/entrypoint.sh#L52 (or somewhere else in the "Getting HEAD info..." section). |
Here is the full output:
|
You're right, I can confirm that this is the case for pull_request* based events |
@jackton1 I guess this needs a release before it can be used. Feel free to poke me when that happens (I'm already using |
@solarmosaic-kflorence A new release should be available now https://github.com/tj-actions/changed-files/releases/tag/v11.1. Thanks |
Fix confirmed, thanks! |
Is this feature missing in the latest version?
Is your feature request related to a problem? Please describe.
Using this on a monorepo with a lot of tags, it will cause minor slowness and more output over time (there are already hundreds of tags).
Describe the solution you'd like?
Tags don't seem to be necessary, so fetching can most likely be performed with
--no-tags
.https://github.com/tj-actions/changed-files/blob/main/entrypoint.sh#L52
Describe alternatives you've considered?
No response
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: