You're welcome. Was still doing it as of last night - has the potential to seriously freak people out I would think.
We're doing pull request/approve pretty often, so give us a heads up if you want us to help test.
Issue #4124 was marked as a duplicate of this issue.
Issue #4126 was marked as a duplicate of this issue.
To clarify, this issue ONLY affects the notifications being sent out. At no point does anyone else have access to your repositories or data.
Issue #4142 was marked as a duplicate of this issue.
Issue #4199 was marked as a duplicate of this issue.
Issue #4231 was marked as a duplicate of this issue.
This is causing information leakage for us. We have a corporate account that owns each of our repos. There are some worker accounts which have access to private client repos to support CI. These are named as per the client. We also have an open source project. When I accept pull requests on the open source project, it sends out notifications revealing the names of some of our clients.
Former userAccount Deleted
Ours aren't even related - we've got people we've never heard of and who are completely unrelated to us accepting our pull requests.
Any word on a fix for this guys?
Er, Anonymous comment #11 was me - forgot to login...
Issue #4239 was marked as a duplicate of this issue.
We are using Issues service and issue's comments generated by accepted pull requests are also attributed to a random user. This comments are also shown on a dashboard of this user. However commits are attributed to right person.