mirror of
https://github.com/keymanapp/keyman.git
synced 2026-09-06 07:37:40 +00:00
d8f81cbdf1
Fixes #6391. The issue here was quite nuanced: where we merged a PR, and then merged the changes into an earlier PR, but left it open, the earlier PR could end up getting the release information comment from keyman-server instead of the later, merged PR. This was because the commit would appear in both PRs, so GitHub would report on both of them. This is not a 100% fix -- but it should stop the PR tagging on unmerged pull requests. The one situation where this may leave a gap is where we have multiple PRs merged on the same day, where a later PR's changes are merged into an earlier PR; in this case I think it is possible that one of the PRs will not get the informative version comment. But given the current fix should avoid the more common situation, I am comfortable to leave it as is for now. This is only informative data... and a more complete fix is a distraction.
38 lines
873 B
TypeScript
38 lines
873 B
TypeScript
export function findLastHistoryPR(base: string) {
|
|
return `
|
|
query FindLastPR {
|
|
search(query: "is:pr is:merged sort:created-desc repo:keymanapp/keyman author:keyman-server label:auto \\"auto: increment\\" base:${base}", last: 1, type: ISSUE) {
|
|
nodes {
|
|
... on PullRequest {
|
|
number
|
|
mergeCommit {
|
|
oid
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
`;
|
|
};
|
|
|
|
export const getAssociatedPR = `
|
|
query associatedPRs($sha: String!) {
|
|
repository(name: "keyman", owner: "keymanapp") {
|
|
commit: object(expression: $sha) {
|
|
... on Commit {
|
|
parents(last: 1) {
|
|
nodes {
|
|
associatedPullRequests(last: 10) {
|
|
nodes {
|
|
state
|
|
title
|
|
number
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
`;
|