Hi Jonathan!
On Dec 1, 2020, at 8:22 AM, Jonathan Bedard via webkit-dev <webkit-dev@lists.webkit.org> wrote:
Hello contributors,
I am in the process of modifying one of our Git mirrors of the repository for permanent use. As part of that modification, I am repairing authorship of historical commits based on contributors.json. This effort includes our branches and resolving commits attributed to commit-queue but authored by contributors. Once this task of rewriting history is completed, I will push the new repository to GitHub to replace the broken mirror that currently resides there.
Does it mean that https://github.com/WebKit/WebKit <https://github.com/WebKit/WebKit> will become an usual repository (not GitHub sync-ed mirror repository) which is mirrored by ourselves? Previously, when I tried, GitHub-mirrored repository does not invoke web-hooks correctly, and it was the reason why I needed to create WKR bots. But if WebKit in GitHub repository becomes an usual repository (while it is mirrored, it is not mirrored by GitHub side), I think this is a good timing to setting up GitHub <-> slack integration to put commits into #changes and retiring WKR bot (while WebKitBot exists). -Yusuke
Since the new repository will have correctly attributed commits, now is a good time to ensure that the email address (or addresses) that you use or have used to contribute to WebKit are attached to your GitHub account, since this is how GitHub connects a user to their contributions.
Also note that GitHub will still just be a mirror for the next few months, so there is no requirement to have an account with GitHub yet.
Jonathan _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev