After reviewing this issue, we determined that it was low priority and unlikely to be worked on in the near future. We appreciate your input, but want to be transparent about our decision to not fix this right now. 

I got this pull request, and I pushed the commits to my repository directly. I was pretty sure this was supposed to automatically close the request, but nothing happened to it whatsoever. Why? And could an admin mark that PR as merged manually now?

Issue BCLOUD-7168 was marked as a duplicate of this issue.

Want to add my concurrence here as well! I'd be happy to have an "Integrated" button or somesuch that indicated that the changeset was integrated in a way that the webui can't detect. Could even include the changeset ID if that helped.

actually now that I look back at this, it seems that it doesn't merge only when I have to "git rebase master" after a "git pull --rebase"

I think this is what I'm looking for as well. My team all maintain a fork of the master project which only I have access to, and we use the pull requests to indicate that a feature is complete and should be merged in. After the relevant parties have approved the pull request, I then go to my local master checkout and "git pull --rebase <fork> <branch>" followed by a "git rebase master" (if needed) and pull the changes in that way. Unfortunately, this leaves us with a bunch of empty pull requests. For the meantime, I've been declining them with a message "rebase merged," but it would be great if we could capture that what really happened is that the pull request was merged in, just not with merge + an extra merge message