chore(deps): bump @actions/github from 5.1.1 to 6.0.0 #300

dependabot · 2023-10-11T05:37:45Z

Bumps @actions/github from 5.1.1 to 6.0.0.

Changelog

Sourced from @actions/github's changelog.

6.0.0

Support the latest Octokit in @actions/github #1553

Drop support of NodeJS v14, v16

Commits

See full diff in compare view

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

github-actions · 2023-10-11T05:38:00Z

Current branch is dependabot/npm_and_yarn/actions/github-6.0.0.
(execution 6478441341 / attempt 1)

github-actions · 2023-10-11T05:38:06Z

Comment Pull Request - GitHub Actions

What is it ?

A GitHub action that comments with a given message the pull request linked to the pushed branch.
You can even put dynamic data thanks to Contexts and expression syntax.

Usage

Classic usage

on: pull_request

jobs:
  example_comment_pr:
    runs-on: ubuntu-latest
    name: An example job to comment a PR
    steps:
      - name: Checkout
        uses: actions/checkout@v3

      - name: Comment PR
        uses: thollander/actions-comment-pull-request@v2
        with:
          message: |
            Hello world ! :wave:

Comment a file content

Thanks to the filePath input, a file content can be commented.
You can either pass an absolute filePath or a relative one that will be by default retrieved from GITHUB_WORKSPACE.
(Note that if both a message and filePath are provided, message will take precedence.)

- name: PR comment with file
  uses: thollander/actions-comment-pull-request@v2
  with:
    filePath: /path/to/file.txt

Setting reactions

You can also set some reactions on your comments through the reactions input.
It takes only valid reactions and adds it to the comment you've just created. (See https://docs.github.com/en/rest/reactions#reaction-types)

- name: PR comment with reactions
  uses: thollander/actions-comment-pull-request@v2
  with:
    message: |
      Hello world ! :wave:
    reactions: eyes, rocket

Specifying which pull request to comment on

You can explicitly input which pull request should be commented on by passing the pr_number input.
That is particularly useful for manual workflow for instance (workflow_run).

...
- name: Comment PR
  uses: thollander/actions-comment-pull-request@v2
  with:
    message: |
      Hello world ! :wave:
    pr_number: 123 # This will comment on pull request #123

Update a comment

Editing an existing comment is also possible thanks to the comment_tag input.

Thanks to this parameter, it will be possible to identify your comment and then to upsert on it.
If the comment is not found at first, it will create a new comment.

That is particularly interesting while committing multiple times in a PR and that you just want to have the last execution report printed. It avoids flooding the PR.

...
- name: Comment PR with execution number
  uses: thollander/actions-comment-pull-request@v2
  with:
    message: |
      _(execution **${{ github.run_id }}** / attempt **${{ github.run_attempt }}**)_
    comment_tag: execution

Note: the input mode can be used to either upsert (by default) or recreate the comment (= delete and create)

Delete a comment

Deleting an existing comment is also possible thanks to the comment_tag input combined with mode: delete.

This will delete the comment at the end of the job.

...
- name: Write a comment that will be deleted at the end of the job
  uses: thollander/actions-comment-pull-request@v2
  with:
    message: |
      The PR is being built...
    comment_tag: to_delete
    mode: delete

Inputs

Action inputs

Name	Description	Required	Default
`GITHUB_TOKEN`	Token that is used to create comments. Defaults to ${{ github.token }}	✅
`message`	Comment body
`filePath`	Path of the file that should be commented
`reactions`	List of reactions for the comment (comma separated). See https://docs.github.com/en/rest/reactions#reaction-types
`pr_number`	The number of the pull request where to create the comment		current pull-request/issue number (deduced from context)
`comment_tag`	A tag on your comment that will be used to identify a comment in case of replacement
`mode`	Mode that will be used to update comment (upsert/recreate/delete)		upsert
`create_if_not_exists`	Whether a comment should be created even if `comment_tag` is not found		true

Permissions

Depending on the permissions granted to your token, you may lack some rights.
To run successfully, this actions needs at least :

permissions: 
   pull-requests: write

Add this in case you get Resource not accessible by integration error.
See jobs.<job_id>.permissions for more information.

Note that, if the PR comes from a fork, it will have only read permission despite the permissions given in the action for the pull_request event.
In this case, you may use the pull_request_target event. With this event, permissions can be given without issue (the difference is that it will execute the action from the target branch and not from the origin PR).

Contributing

Build

The build steps transpiles the src/main.ts to lib/index.js which is used in a NodeJS environment.
It is handled by vercel/ncc compiler.

$ npm run build

github-actions · 2023-10-11T05:38:08Z

Content of file referenced with absolute path

thollander · 2024-10-10T20:26:07Z

@dependabot rebase

Bumps [@actions/github](https://github.com/actions/toolkit/tree/HEAD/packages/github) from 5.1.1 to 6.0.0. - [Changelog](https://github.com/actions/toolkit/blob/main/packages/github/RELEASES.md) - [Commits](https://github.com/actions/toolkit/commits/HEAD/packages/github) --- updated-dependencies: - dependency-name: "@actions/github" dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>

github-actions · 2024-10-10T20:27:19Z

Current branch is dependabot/npm_and_yarn/actions/github-6.0.0.
(execution 11281484161 / attempt 1)

github-actions · 2024-10-10T20:27:23Z

Comment Pull Request - GitHub Actions

What is it ?

A GitHub action that comments with a given message the pull request linked to the pushed branch.
You can even put dynamic data thanks to Contexts and expression syntax.

Usage

Classic usage

on: pull_request

jobs:
  example_comment_pr:
    runs-on: ubuntu-latest
    name: An example job to comment a PR
    steps:
      - name: Checkout
        uses: actions/checkout@v3

      - name: Comment PR
        uses: thollander/actions-comment-pull-request@v3
        with:
          message: |
            Hello world ! :wave:

Comment a file content

Thanks to the filePath input, a file content can be commented.
You can either pass an absolute filePath or a relative one that will be by default retrieved from GITHUB_WORKSPACE.
(Note that if both a message and filePath are provided, message will take precedence.)

- name: PR comment with file
  uses: thollander/actions-comment-pull-request@v3
  with:
    filePath: /path/to/file.txt

Setting reactions

You can also set some reactions on your comments through the reactions input.
It takes only valid reactions and adds it to the comment you've just created. (See https://docs.github.com/en/rest/reactions#reaction-types)

- name: PR comment with reactions
  uses: thollander/actions-comment-pull-request@v3
  with:
    message: |
      Hello world ! :wave:
    reactions: eyes, rocket

Specifying which pull request to comment on

You can explicitly input which pull request should be commented on by passing the pr_number input.
That is particularly useful for manual workflow for instance (workflow_run).

...
- name: Comment PR
  uses: thollander/actions-comment-pull-request@v3
  with:
    message: |
      Hello world ! :wave:
    pr_number: 123 # This will comment on pull request #123

Update a comment

Editing an existing comment is also possible thanks to the comment_tag input.

Thanks to this parameter, it will be possible to identify your comment and then to upsert on it.
If the comment is not found at first, it will create a new comment.

That is particularly interesting while committing multiple times in a PR and that you just want to have the last execution report printed. It avoids flooding the PR.

...
- name: Comment PR with execution number
  uses: thollander/actions-comment-pull-request@v3
  with:
    message: |
      _(execution **${{ github.run_id }}** / attempt **${{ github.run_attempt }}**)_
    comment_tag: execution

Note: the input mode can be used to either upsert (by default) or recreate the comment (= delete and create)

Delete a comment

Deleting a comment with a specific comment_tag is possible with the mode: delete. If a comment with the comment_tag exists, it will be deleted when ran.

...
- name: Delete a comment
  uses: thollander/actions-comment-pull-request@v3
  with:
    comment_tag: to_delete
    mode: delete

Delete a comment on job completion

Deleting an existing comment on job completion is also possible thanks to the comment_tag input combined with mode: delete-on-completion.

This will delete the comment at the end of the job.

...
- name: Write a comment that will be deleted at the end of the job
  uses: thollander/actions-comment-pull-request@v3
  with:
    message: |
      The PR is being built...
    comment_tag: to_delete_on_completion
    mode: delete-on-completion

Inputs

Action inputs

Name	Description	Required	Default
`github-token`	Token that is used to create comments. Defaults to ${{ github.token }}	✅
`message`	Comment body
`file-path`	Path of the file that should be commented
`reactions`	List of reactions for the comment (comma separated). See https://docs.github.com/en/rest/reactions#reaction-types
`pr-number`	The number of the pull request where to create the comment		current pull-request/issue number (deduced from context)
`comment-tag`	A tag on your comment that will be used to identify a comment in case of replacement
`mode`	Mode that will be used to update comment (upsert/recreate/delete/delete-on-completion)		upsert
`create-if-not-exists`	Whether a comment should be created even if `comment-tag` is not found		true

Outputs

Action outputs

You can get some outputs from this actions :

Name	Description
`id`	Comment id that was created or updated
`body`	Comment body
`html-url`	URL of the comment created or updated

Example output

- name: Comment PR
  uses: thollander/actions-comment-pull-request@v3
  id: hello
  with:
    message: |
      Hello world ! :wave:
- name: Check outputs
  run: |
    echo "id : ${{ steps.hello.outputs.id }}"
    echo "body : ${{ steps.hello.outputs.body }}"
    echo "html-url : ${{ steps.hello.outputs.html-url }}"

Permissions

Depending on the permissions granted to your token, you may lack some rights.
To run successfully, this actions needs at least :

permissions: 
   pull-requests: write

Add this in case you get Resource not accessible by integration error.
See jobs.<job_id>.permissions for more information.

Note that, if the PR comes from a fork, it will have only read permission despite the permissions given in the action for the pull_request event.
In this case, you may use the pull_request_target event. With this event, permissions can be given without issue (the difference is that it will execute the action from the target branch and not from the origin PR).

Contributing

Build

The build steps transpiles the src/main.ts to lib/index.js which is used in a NodeJS environment.
It is handled by vercel/ncc compiler.

$ npm run build

github-actions · 2024-10-10T20:27:24Z

Content of file referenced with absolute path

dependabot bot added the dependencies Pull requests that update a dependency file label Oct 11, 2023

thollander approved these changes Oct 10, 2024

View reviewed changes

dependabot bot force-pushed the dependabot/npm_and_yarn/actions/github-6.0.0 branch from 08210c1 to 38af97b Compare October 10, 2024 20:27

thollander merged commit cb13519 into main Oct 10, 2024
3 checks passed

dependabot bot deleted the dependabot/npm_and_yarn/actions/github-6.0.0 branch October 10, 2024 20:28

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): bump @actions/github from 5.1.1 to 6.0.0 #300

chore(deps): bump @actions/github from 5.1.1 to 6.0.0 #300

dependabot bot commented on behalf of github Oct 11, 2023 •

edited

Loading

github-actions bot commented Oct 11, 2023

github-actions bot commented Oct 11, 2023

github-actions bot commented Oct 11, 2023

thollander commented Oct 10, 2024

github-actions bot commented Oct 10, 2024

github-actions bot commented Oct 10, 2024

github-actions bot commented Oct 10, 2024

chore(deps): bump @actions/github from 5.1.1 to 6.0.0 #300

chore(deps): bump @actions/github from 5.1.1 to 6.0.0 #300

Conversation

dependabot bot commented on behalf of github Oct 11, 2023 • edited Loading

6.0.0

github-actions bot commented Oct 11, 2023

github-actions bot commented Oct 11, 2023

Comment Pull Request - GitHub Actions

What is it ?

Usage

Classic usage

Comment a file content

Setting reactions

Specifying which pull request to comment on

Update a comment

Delete a comment

Inputs

Action inputs

Permissions

Contributing

Build

github-actions bot commented Oct 11, 2023

thollander commented Oct 10, 2024

github-actions bot commented Oct 10, 2024

github-actions bot commented Oct 10, 2024

Comment Pull Request - GitHub Actions

What is it ?

Usage

Classic usage

Comment a file content

Setting reactions

Specifying which pull request to comment on

Update a comment

Delete a comment

Delete a comment on job completion

Inputs

Action inputs

Outputs

Action outputs

Example output

Permissions

Contributing

Build

github-actions bot commented Oct 10, 2024

dependabot bot commented on behalf of github Oct 11, 2023 •

edited

Loading