Maybe not exactly a bug, but the merge queue not a...
# report-bugs
b
Maybe not exactly a bug, but the merge queue not actually “merging” PRs on Github also has the side-effect of making release notes broken. Github has an API you can use to generate release notes for a commit range. It lists merged PRs as well as contributors on a release. We use this as our changelog on deployments. Since we enabled the merge queue, it now only picks up PRs that were actually merged in Github. Would Graphite consider a “true merge” option? One way I can imagine this working is by merging down PRs from the top of the stack into their parents until it finally merges into main. This would also restore things like Linear merge triggers.
👍 1
p
(If applicable) To help us repro, please send the following if you haven't already: - PR links, screenshots, and/or debug output if applicable - Repro steps - Does this happen consistently? Just to you or others on your team also? - Is this a regression? Is the problem new? - If you're having an issue with the CLI, please send us debug logs using
gt feedback --with-debug-context <any message>
hey Saad, thanks for you feedback. Will surface to the team
d
Also having this issue after turning on the merge queue, since Githubs auto generate release notes looks at merged PR's and not commits. The solution I went with was https://git-cliff.org/ and had Claude sort out the formatting to match that of the auto generated release notes. Kinda a pain honestly but a decent solution with maybe some more flexibility in the future. 🤷‍♂️