You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is of special interest to @Peranikov, @piruty-joy, seeing that they are working on a Japanese translation. And for anybody else with active forks.
I've rewritten the whole history of the project to hide my emails behind noreply@alexn.org. This is because GitHub has become a spam problem for me and I do not want to expose my real emails anymore. I've followed the tutorial here and have only touched my own commits: https://help.github.com/articles/changing-author-info/
Existing forks have to rebase off the new master, otherwise your branch is going to be divergent. The recipe for doing that goes something like this:
BACKUP
DO NOT start with a git pull
git fetch
git rebase --onto origin/master master <local_branch> (for local each branch)
git pull --force
Sorry for the inconvenience and let me know if you need help.
The text was updated successfully, but these errors were encountered:
This is of special interest to @Peranikov, @piruty-joy, seeing that they are working on a Japanese translation. And for anybody else with active forks.
I've rewritten the whole history of the project to hide my emails behind
noreply@alexn.org
. This is because GitHub has become a spam problem for me and I do not want to expose my real emails anymore. I've followed the tutorial here and have only touched my own commits: https://help.github.com/articles/changing-author-info/Existing forks have to rebase off the new master, otherwise your branch is going to be divergent. The recipe for doing that goes something like this:
git pull
git fetch
git rebase --onto origin/master master <local_branch>
(for local each branch)git pull --force
Sorry for the inconvenience and let me know if you need help.
The text was updated successfully, but these errors were encountered: