[Bug]: Github Action Commit Username does not match PAT_USERNAME
Is there an existing issue for the same bug? (If one exists, thumbs up or comment on the issue instead).
- [x] I have checked the existing issues.
Describe the bug and reproduction steps
If I use the Github Actions Workflow, and set PAT_TOKEN, commits marked as openhands-agent instead of using the value from PAT_USERNAME.
If I set PAT_USERNAME, commits should come from that username.
OpenHands Installation
GitHub resolver
OpenHands Version
0.37.0
Operating System
None
Logs, Errors, Screenshots, and Additional Context
Hi @tdickman, I believe this behavior is intended
We want to ensure resolver commits are associated with the agent (for traceability)
The PR, however, when opened is under PAT_USERNAME. This is to ensure the person who requested the resolver job can't approve the resulting PR and bypass the review process
@malhotra5 got it. We are using a robot account for the github action / resolver, so the pull request comes from company-robot, but commits come from openhands-agent. We are hoping to have multiple people working in the repository use the github action, so it feels weird to have it under a single person's account (and also feels weird to have the pull request and commits with different usernames).
@malhotra5 If I understand the complaint, it is the the openhands-agent does not have a published PGP sigs and is not configured on openhands cloud to sign commits. I have the same issue, though I think it would be a feature request rather than a bug. If I have misunderstood @tdickman, I'll open a separate PR for that.
IMHO it's important to solve as many repos do not allow unsigned commits. Which means I have to rebase and make my self the author of open-hands agent commits.
This issue is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.
This issue is stale because it has been open for 40 days with no activity. Remove the stale label or leave a comment, otherwise it will be closed in 10 days.
This issue is stale because it has been open for 40 days with no activity. Remove the stale label or leave a comment, otherwise it will be closed in 10 days.
This issue was automatically closed due to 50 days of inactivity. We do this to help keep the issues somewhat manageable and focus on active issues.