Difference between revisions of "Migrating tools to GitHub"
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
# Run <code>cd apertium-on-github</code>. |
# Run <code>cd apertium-on-github</code>. |
||
# Do '''only the first four steps''' described [https://github.com/apertium/apertium-on-github#migration here]. |
# Do '''only the first four steps''' described [https://github.com/apertium/apertium-on-github#migration here]. |
||
| − | # Run <code>./import-repo.sh "<nowiki>trunk/<tool-name></nowiki>" "<tool-name>" |
+ | # Run <code>./import-repo.sh "<nowiki>trunk/<tool-name></nowiki>" "<tool-name>" "apertium-tools"</code>. |
And that's it! |
And that's it! |
||
Latest revision as of 04:45, 9 March 2018
Apertium has migrated all the language data, the core, and a few tools to GitHub. Many tools have not been migrated because they are not frequently maintained and/or are outdated. Read-only versions of these tools are available at their old SVN locations.
If there is a tool that has not been migrated but you would like to have it migrated, you have two options.
Contents
Do it yourself[edit]
If the tool is under a personal GitHub account[edit]
If the tool is already on GitHub under your personal account, you can transfer it to the 'apertium' organization. Please send an email to the apertium-stuff mailing list immediately after you do this.
If the tool is not already on GitHub[edit]
If the tool is not already on GitHub:
- Run
git clone https://github.com/apertium/apertium-on-github.git. - Run
cd apertium-on-github. - Do only the first four steps described here.
- Run
./import-repo.sh "trunk/<tool-name>" "<tool-name>" "apertium-tools".
And that's it!
Ask for it to be migrated[edit]
Please send an email to the apertium-stuff mailing list about your tool.
