Skip to content
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

Document the use of fetch-depth in tj-actions/changed-files #5373

Closed
gustavovalverde opened this issue Oct 10, 2022 · 1 comment
Closed

Document the use of fetch-depth in tj-actions/changed-files #5373

gustavovalverde opened this issue Oct 10, 2022 · 1 comment
Labels
A-devops Area: Pipelines, CI/CD and Dockerfiles A-docs Area: Documentation C-enhancement Category: This is an improvement

Comments

@gustavovalverde
Copy link
Member

Motivation

We've been dealing with multiple issues related to tj-actions/changed-files and file comparison using previous the previous sha. We should document the actual configuration and why it's the one for our use case

Related Work

#5367 (comment)

@gustavovalverde gustavovalverde added A-docs Area: Documentation A-devops Area: Pipelines, CI/CD and Dockerfiles C-enhancement Category: This is an improvement S-needs-triage Status: A bug report needs triage P-Low ❄️ labels Oct 10, 2022
@gustavovalverde
Copy link
Member Author

After a few merges we've done recently, this is no longer needed as the arguments were removed and the default behavior is as expected.

@mpguerra mpguerra removed the S-needs-triage Status: A bug report needs triage label Mar 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-devops Area: Pipelines, CI/CD and Dockerfiles A-docs Area: Documentation C-enhancement Category: This is an improvement
Projects
None yet
Development

No branches or pull requests

2 participants