Skip to content

Change Github Action permissions#3465

Closed
danpawlik wants to merge 1 commit into
openstack-k8s-operators:mainfrom
danpawlik:improve-verify-gh-action
Closed

Change Github Action permissions#3465
danpawlik wants to merge 1 commit into
openstack-k8s-operators:mainfrom
danpawlik:improve-verify-gh-action

Conversation

@danpawlik

@danpawlik danpawlik commented Nov 7, 2025

Copy link
Copy Markdown
Contributor

Currently the commit-message-validator.yml Github Action raise an issue
when the commit message is improper:

Resource not accessible by integration

Let's try if this would help.

@danpawlik danpawlik requested a review from a team as a code owner November 7, 2025 10:09
@openshift-ci

openshift-ci Bot commented Nov 7, 2025

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@danpawlik danpawlik force-pushed the improve-verify-gh-action branch 6 times, most recently from f5031e1 to 0fed78b Compare November 7, 2025 10:29
@danpawlik danpawlik changed the title Making a test - improve GH job Change Github Action permissions Nov 7, 2025
@danpawlik danpawlik force-pushed the improve-verify-gh-action branch 7 times, most recently from d3a2dbc to 605e130 Compare November 7, 2025 11:02
@danpawlik danpawlik force-pushed the improve-verify-gh-action branch from 605e130 to 48d9e7b Compare November 7, 2025 11:40
Currently the commit-message-validator.yml Github Action raise an issue
when the commit message is improper:

    Resource not accessible by integration

Let's try if this would help.

Signed-off-by: Daniel Pawlik <dpawlik@redhat.com>

@michburk michburk left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested in my own fork: michburk#2
The commit body workflow seems to trigger twice on each event (make sure to check the collapsed "1 similar comment" sections in the above pr), and there are extra 'my comment' comments.

owner: context.repo.owner,
repo: context.repo.repo,
issue_number: context.issue.number,
body: 'my comment'

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This adds an additional my comment comment from the bot on the pr

on:
pull_request_target:
types: [opened, synchronize, edited, reopened]
pull_request:

@michburk michburk Nov 11, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think running on both pull_request_target AND pull_request [open/sync/edit/reopen] means the workflow will run twice for each event, leaving two comments instead of one. Maybe we could just trigger on pull_request_target?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried, nothing helped.

@github-actions

Copy link
Copy Markdown

This PR is stale because it has been for over 15 days with no activity.
Remove stale label or comment or this will be closed in 7 days.

@openshift-merge-robot

Copy link
Copy Markdown
Contributor

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@github-actions github-actions Bot removed the Stale label Nov 30, 2025
@danpawlik danpawlik closed this Dec 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants