TEST Translator process

Table of Contents

1. Tasks - new languages
2. Tasks - existing languages

---

Tasks for new languages

1. Add a project

2. Create initial issue

3. Fork repo

4. Make the edits (e.g. editing About.md) and commit.

1. If you want to link your commit and PR to issue, refer to issue number in commit message. E.g. #100 - Create about

2. If you want to close an issue automatically on merged PR (i.e. skip step 8), add one of close, closes, closed, fix, fixes, fixed, resolve, resolves, resolved keywords and issue number in your PR title. E.g. Resolve #100 - Create about. Read more detail here

3. NOTE: Don't do the above if an issue requires more than your commits. For example, an English source change that needs all translations.

5. Keep your repo up to date with upstream/original

A fork only has the version of the files at the time of forking. It will goes out of sync when someone else merges PR to upstream (the original repository). You need to keep your fork up to date before you create a commit.

1. If you use GitBash or Mac terminal:

   1. Add the remote, call it "upstream", you only need to do this once:

      git remote add upstream https://github.com/necsi/source-translation-text.git
      

      or

      git remote add upstream [email protected]:necsi/source-translation-text.git
      

   2. After committing your change in step 4, rebase your changes onto upstream/master

      git pull --rebase upstream master
      

   3. Push your changes to your fork

2. To do it from browser:

   1. Open your fork repo, click on Compare

   2. Click switching the base

   3. You will see a list of commits if there are changes upstream that are not in your fork. Click Create pull request

   4. Give PR a title and may be description, then click Create pull request

   5. Scroll to the bottom to select the correct option

   6. After selecting the correct option, click Rebase and merge

   7. Confirm the merge

   8. You'll see this on successful merge

6. Request a pull request

7. (the admin then perform a merge (see WIKI ADMIN TBA LINK)

| |

8. Close issue after PR is merged

This step may be skipped if you use keyword in #4

| |

Tasks for existing languages

1. Create an issue before working on a file, assign self or someone else, connect to Project. See Create initial issue

2. If issue already exists and is not assigned to someone else in your team, you can assign to yourself if you want.

3. Add commit, Rebase to upstream, request PR

4. Close issue after PR is merged (may not need if you use keyword).

5. For issue with checkboxes such as English source has change that needs all translations, make sure you check off your language after merged PR.