Uh oh!
There was an error while loading. Please reload this page.
This repository was archived by the owner on Aug 6, 2026. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ghLoginis null and agent views a recent PR it didn't createWhen
ghLoginis null (all cloud/App-token runs), the author check is skipped entirely and recency alone gates attribution. If the agent encounters a PR URL in its terminal output (e.g. fromgh pr viewor a tool that prints a related PR) that was created by someone else within the 5-minute window, it will be attributed to this run. The existing test"does not attribute a fresh PR authored by someone else"only exercises the case whereghLoginis resolved; there's no test forghLogin = null+prAuthor = "some-human"+prCreatedAt = justNow(). Adding that case would confirm (or surface) the current behavior for that path.