Skip to content

Fix fetch_refs assigning same tag to both old_ref and new_ref - #975

Merged
l8556 merged 1 commit into
masterfrom
fix/fetch-refs-same-tag-bug
Jun 29, 2026
Merged

l8556 merged 1 commit into
masterfrom
fix/fetch-refs-same-tag-bug

Conversation

@trofim24

Copy link
Copy Markdown
Contributor

fetch_refs used latest_tag (per_page: 1) for both refs, so old_ref == new_ref always, producing no diff output.

Now fetch_refs only fills new_ref from latest tag (for single-ref usage like /get_changes v1.0). When no refs are provided, bot returns a message asking user to specify versions.

Also add usage examples to README.

@trofim24
trofim24 force-pushed the fix/fetch-refs-same-tag-bug branch 2 times, most recently from 1ee5e23 to 182becb Compare June 29, 2026 08:47
fetch_refs used latest_tag (per_page: 1) for both refs, so
old_ref == new_ref always, producing no diff output.

Now fetch_refs only fills new_ref from latest tag (for single-ref
usage like `/get_changes v1.0`). When no refs are provided, bot
returns a message asking user to specify versions.

Also add usage examples to README.
@trofim24
trofim24 force-pushed the fix/fetch-refs-same-tag-bug branch from 182becb to 95c1c5f Compare June 29, 2026 09:31
@l8556
l8556 merged commit a5153c5 into master Jun 29, 2026
6 checks passed
@l8556
l8556 deleted the fix/fetch-refs-same-tag-bug branch June 29, 2026 20:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants