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

chore(deps): update tj-actions/changed-files action to v44 #261

Merged
merged 1 commit into from
Mar 27, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 27, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
tj-actions/changed-files action major v43 -> v44

Release Notes

tj-actions/changed-files (tj-actions/changed-files)

v44

Compare Source

Changes in v44.0.0
🔥🔥 BREAKING CHANGE 🔥🔥
Overview

We've made a significant update to how pull requests (PRs) from forked repositories are processed. This improvement not only streamlines the handling of such PRs but also fixes a previously identified issue.

Before the Change

Previously, when you created a pull request from a forked repository, any files changed in the target branch after the PR creation would erroneously appear as part of the PR's changed files. This made it difficult to distinguish between the actual changes introduced by the PR and subsequent changes made directly to the target branch.

What Has Changed

With this update, a pull request from a fork will now only include the files that were explicitly changed in the fork. This ensures that the list of changed files in a PR accurately reflects the contributions from the fork, without being muddled by unrelated changes to the target branch.

Important Note for Users

To take advantage of this new behaviour, it's necessary to specify the fork repository explicitly when performing the checkout step in your workflows. Below is an example configuration that demonstrates how to do this:

- uses: actions/checkout@v4
  with:
    repository: ${{ github.event.pull_request.head.repo.full_name }}

This modification ensures that your workflows correctly identify and interact with the source repository for PRs originating from forks.


What's Changed
New Contributors

Full Changelog: tj-actions/changed-files@v43.0.1...v44.0.0



Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added dependencies merge when passing Merge the PR automatically once all status checks have passed labels Mar 27, 2024
Copy link

codecov bot commented Mar 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.50%. Comparing base (5bec452) to head (9b109ee).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #261   +/-   ##
=======================================
  Coverage   87.50%   87.50%           
=======================================
  Files           4        4           
  Lines         408      408           
=======================================
  Hits          357      357           
  Misses         51       51           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@repo-ranger repo-ranger bot merged commit 75d05e4 into main Mar 27, 2024
27 checks passed
@delete-merged-branch delete-merged-branch bot deleted the renovate/tj-actions-changed-files-44.x branch March 27, 2024 03:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies merge when passing Merge the PR automatically once all status checks have passed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant