Skip to content

CI: Query base.ref instead of sha for milestone VERSION resolution - #7463

Merged
echoix merged 2 commits into
OSGeo:mainfrom
ArthPatel1502:fix/assign-milestone-target-7374
Jun 7, 2026
Merged

echoix merged 2 commits into
OSGeo:mainfrom
ArthPatel1502:fix/assign-milestone-target-7374

Conversation

@ArthPatel1502

Copy link
Copy Markdown
Contributor

Closes #7374. Updates the milestones workflow to look up the version file using the target PR base branch ref instead of the commit SHA.

Comment thread .github/workflows/milestones.yml Resolved
@github-actions github-actions Bot added the CI Continuous integration label Jun 1, 2026
@ArthPatel1502
ArthPatel1502 force-pushed the fix/assign-milestone-target-7374 branch from 4e66ed8 to 5736524 Compare June 5, 2026 03:58
@echoix
echoix merged commit 2ff607f into OSGeo:main Jun 7, 2026
27 checks passed
@github-actions github-actions Bot added this to the 8.6.0 milestone Jun 8, 2026
ninsbl pushed a commit to ninsbl/grass that referenced this pull request Jul 7, 2026
…SGeo#7463)

Updates the milestones workflow to look up the version file using the merge commit SHA instead of the default branch commit SHA returned since the changes of November 2025 to `pull_request_target`. The merge commit sha exists before and after a PR is merged, but we are using it only after a PR is merged. Even if the way a PR is merged is not "merge", like squash&merge or rebase&merge, the commit of the target branch right after the PR is merged (including that one) is returned, which is what is wanted here.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI Continuous integration

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Revise Assign Milestone Workflow

2 participants