(manage repo configuration) mrconfig
Used to manage translation updates for NVDA and NVDA add-ons.
For information on having add-ons added to the nvda-addons website: https://github.com/nvaccess/addonFiles#readme
- The add-on repo must contain a branch named
stable
. The translation system uses thestable
branch to sending/receiving translation updates to/from NVDA translation repo. - Ask for the add-on to be included in the translation system via the NVDA add-ons mailing list.
- A member of the NVDA add-on team creates a repo for the add-on at NVDA Addons GitHub
- The member of the NVDA add-on team should confirm there is a branch
stable
- Create an issue on nvaccess/mrconfig asking for the addon to be included.
- NV Access staff will update the server:
cd mr
mr up
cd available.d
mr registerAddon addonRepoName
git push
cd ../
(mr dir)mr up
cd addons/addonRepoName
mr addon2settings
cd ../../mr/srt
svn commit */settings -m "Make <addonName> add-on available for translation."
- NV Access staff will edit
mr/automatic.crontab
- Copy one of the lines for one of the existing addons, just change the addon name and paste it in the correct section, commit and push.
- Note: Run line from crontab manually to confirm.
- NV Access staff will update the server:
Note: Maintainers may follow other procedures. This info is provided for convenience, according to discussions like this topic about repos management.
- Clone the maintainer repo:
git clone https://github.com/githubUserName/addonRepoName
- Add remote for GitHub/nvdaaddons repo:
git remote add nvdaaddons https://github.com/nvdaaddons/addonRepoName
- Fetch the GitHub/nvdaaddons repo:
git fetch nvdaaddons
- Track the stable branch:
git checkout -t nvdaadons/stable
- Periodically:
- From stable branch:
git pull
# Get translationsgit merge master
# Stable code containing translatable messagesgit push nvdaaddons stable
- From master:
git pull
git merge stable
git push origin master
# Update translations
- From stable branch: