12-31-2013, 09:20 PM
TulipVorlax, I checked you master repository and it is out-of-date. I think that is a good habit preserve it in synchronism with dgud's one. So, after the last version be released it's a good idea rebase your master branch.
There are a small reference guide for git commands in this thread: Working with GitHub repository
You will find there a session named: "Updating your master branch with the official one"
After you have your master branch updated, I think that it could be useful you create a new branch only for version translation. In the past, they suggested me to prefix the branch with my initials (mv) like this: mv/buf_fix_1.5.2. Maybe you could use something like that.
Then, you can make the translations file-by-file. You can commit at any time. You can push it to your git repository, but you only make a pull request after you have finished translating all files you think be necessary or adding new ones.
This way, you don't need to create one branch for each file you are correcting.
I hope this could help you. I'm not the expert, but I can share what I've learned until now.
There are a small reference guide for git commands in this thread: Working with GitHub repository
You will find there a session named: "Updating your master branch with the official one"
After you have your master branch updated, I think that it could be useful you create a new branch only for version translation. In the past, they suggested me to prefix the branch with my initials (mv) like this: mv/buf_fix_1.5.2. Maybe you could use something like that.
Then, you can make the translations file-by-file. You can commit at any time. You can push it to your git repository, but you only make a pull request after you have finished translating all files you think be necessary or adding new ones.
This way, you don't need to create one branch for each file you are correcting.
I hope this could help you. I'm not the expert, but I can share what I've learned until now.