Skip to content

list_commits on a feature branch: my own commits get filtered out #27473

@ahmadabdalla

Description

@ahmadabdalla

Question about how the integrity filter is supposed to behave, before I change my workflow config.

What I'm doing I have a workflow that reads commits on my dev branch (so it can write release notes) using list_commits. The repo is public. My default branch is main. I haven't set min-integrity, so I get the public-repo default, which is approved.

What's happening 28 commits get filtered out. The log entry for each one looks like this:

 {
   "tool_name": "list_commits",
   "author_login": "ahmadabdalla",
   "integrity_tags": ["none:all"],
   "reason": "...lower integrity than agent requires...\"approved\""
 }

The author (ahmadabdalla) is me (owner). The commits are on dev, not yet on main.

What I expected Reading the integrity docs, I thought commits I authored myself would count as approved and come through. They don't, they're tagged none and blocked.

My question Is this the intended behavior for commits that aren't yet on the default branch? If yes, what's the recommended way to let a workflow read its own owner's commits on a feature branch, and set min-integrity: none, or is there a more targeted setting I'm missing?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions