| Summary: | Please disable direct commits to the github mirror | ||
|---|---|---|---|
| Product: | Services | Reporter: | Yuri Victorovich <yuri> |
| Component: | Git Integration | Assignee: | Ulrich Spörlein <uqs> |
| Status: | Closed Not A Bug | ||
| Severity: | Affects Only Me | CC: | uqs |
| Priority: | --- | ||
| Version: | unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
Yuri Victorovich
2019-06-19 18:34:17 UTC
The user obviously has no commit access to our repo. What you link to is basically a pull request. Note that the URL you show doesn't have any branch information, so this commit is not part of any branch of our repo. It is a pull request that you can see here: https://github.com/myfreeweb/freebsd-ports-dank/pull/4 What sort of notification were you getting? (In reply to Ulrich Spoerlein from comment #1) What's confusing is that "dank" isn't mentioned anywhere, only freebsd/freebsd-ports is mentioned. GitHub doesn't have a pull request in this repository, yet it notifies users from this repository about something happening in some other repository as if it happens here. This port is present there but not in FreeBSD: https://github.com/myfreeweb/freebsd-ports-dank/blob/lite/x11/tilix, which is weird. (In reply to Ulrich Spoerlein from comment #1) > What sort of notification were you getting? It was just like a comment on the thing I am watching in the repository, except this repository was obviously not our repository. --------------------------- Hi, First thanks for porting tilix ( the best terminal emulator for me ). For the patch in lang/ldc, i'm on freebsd 12 and when i link tilix, i have an intrinsics error on memcpy, this is why i downgrade compiler to clang-6. PS: sorry for my poor english. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread. ---- The links pointing back to https://github.com/freebsd/freebsd-ports/commit/... I believe that this event resulted from some bug in GitHub. I notified GitHub about this through the private message to their customer service. Closing this problem here: Not A Bug in FreeBSD's infrastructure. |