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

Bump tj-actions/changed-files from 43 to 44 #371

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 27, 2024

Bumps tj-actions/changed-files from 43 to 44.

Release notes

Sourced from tj-actions/changed-files's releases.

v44

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


v44.0.0

🔥🔥 BREAKING CHANGE 🔥🔥

... (truncated)

Changelog

Sourced from tj-actions/changed-files's changelog.

Changelog

43.0.1 - (2024-03-20)

🐛 Bug Fixes

  • Remove warning with detecting the local git repository when using Github's REST API (#2002) (077b23f) - (Tonye Jack)

📦 Bumps

  • Bump @​typescript-eslint/eslint-plugin from 7.3.0 to 7.3.1 (#1995)

Signed-off-by: dependabot[bot] [email protected] Co-authored-by: dependabot[bot] Co-authored-by: repo-ranger[bot] (5c6aa49) - (dependabot[bot])

  • Bump @​typescript-eslint/parser from 7.3.0 to 7.3.1 (#1996)

Signed-off-by: dependabot[bot] [email protected] Co-authored-by: dependabot[bot] (0320702) - (dependabot[bot])

🔄 Update

  • Update README.md (2859a60) - (Tonye Jack)

⚙️ Miscellaneous Tasks

  • deps: Update dependency typescript to v5.4.3 (20576b4) - (renovate[bot])
  • Update inputs.ts adding comment about fetch_depth (#2000) (0276805) - (Tonye Jack)
  • deps: Update dependency @​types/node to v20.11.30 (427adf4) - (renovate[bot])
  • deps: Update dependency @​typescript-eslint/eslint-plugin to v7.3.1 (aa0b62a) - (renovate[bot])
  • deps: Update dependency @​types/node to v20.11.29 (3890368) - (renovate[bot])
  • deps: Update typescript-eslint monorepo to v7.3.0 (98a74d2) - (renovate[bot])
  • deps: Lock file maintenance (068000d) - (renovate[bot])
  • deps: Update dependency @​types/node to v20.11.28 (490ac39) - (renovate[bot])

⬆️ Upgrades

  • Upgraded to v43 (#1990)

Co-authored-by: jackton1 [email protected] (d03038e) - (tj-actions[bot])

43.0.0 - (2024-03-13)

🚀 Features

  • Add support for returning true for any_{changed, modified, deleted} outputs when no patterns are specified (#1988) (a5cf6aa) - (Tonye Jack)

🔄 Update

  • Updated README.md (#1989)

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot requested a review from a team as a code owner March 27, 2024 02:24
@dependabot dependabot bot removed the request for review from a team March 27, 2024 02:24
@dependabot dependabot bot added the 🤖 Dependencies Pull requests that update a dependency file label Mar 27, 2024
Copy link

coderabbitai bot commented Mar 27, 2024

Important

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@efectn
Copy link
Member

efectn commented Apr 6, 2024

@dependabot rebase

Bumps [tj-actions/changed-files](https://github.com/tj-actions/changed-files) from 43 to 44.
- [Release notes](https://github.com/tj-actions/changed-files/releases)
- [Changelog](https://github.com/tj-actions/changed-files/blob/main/HISTORY.md)
- [Commits](tj-actions/changed-files@v43...v44)

---
updated-dependencies:
- dependency-name: tj-actions/changed-files
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/github_actions/tj-actions/changed-files-44 branch from 61e00a8 to 2ce7370 Compare April 6, 2024 11:53
@ReneWerner87 ReneWerner87 merged commit 75dc399 into master Apr 19, 2024
5 of 6 checks passed
@dependabot dependabot bot deleted the dependabot/github_actions/tj-actions/changed-files-44 branch April 19, 2024 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🤖 Dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants