Skip to content

author_association check in example workflows #163

@glicht

Description

@glicht

Hi,

I am testing out the gemini-pr-review workflow from the examples folder.

I noticed that it was being skipped when a pull request is created. The condition that was causing the skip is:

contains(fromJSON('["OWNER", "MEMBER", "COLLABORATOR"]'), github.event.pull_request.author_association)

Link to the line:

contains(fromJSON('["OWNER", "MEMBER", "COLLABORATOR"]'), github.event.pull_request.author_association)

I am in a private repo and the value I get from github.event.pull_request.author_association is CONTRIBUTOR (even though the user opening the PR is a MEMBER).

Might be that this test can be modified to take into consideration the case I experienced.

Additionally, I think in a private repo the test can be skipped. Would love to hear your thoughts about this.

Metadata

Metadata

Labels

kind/bugSomething isn't workingpriority/p2Important but can be addressed in a future release

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions