Meza/Short procedure on how to submit a PR to Meza
Appearance
< Meza
For Meza
[edit]- At github.com
- Log in to your an account at Github.com
- Visit the Meza project page at: https://github.com/nasa/meza
- Create a "Fork" of the official Meza project on your github account
- On your wiki server
cd /opt/meza/
git remote set-url origin https://github.com/<yourgitusername>/meza
- Edit the files you think are wrong or need improved
git push -A "a few words about what your changes are"
- Back at https://github.com/<yourgitusername>/meza
- Verify that the changes you made a reflected in your fork of the meza project
- (optional) - Make a pull request (PR) in github using github gui tools to invite primary extension owner to "pull" your changes into their master repo.
For a specific extension on github
[edit]- On your wiki server
- vi either
/opt/meza/config/core/MezaExtensions.yml
or/opt/conf-meza/public/MezaLocalExtennsions.yml
and identify the repo source and version of the extension you wish to develop
- vi either
- At https://github.com
- Log in to your an account at Github.com
- Visit the extension project page at: https://github.com/<extension owner>/<extension name>
- Create a "Fork" of the official extension project on your github account
- On your wiki server
- cd to
/opt/htdocs/mediawiki/extension/<extension name>
git remote set-url origin https://github.com/<yourgitusername>/<extension name>
- Edit the files you think are wrong or need improved
git push -A "a few words about what your changes are"
- cd to
- Visit
https://github.com/<yourgitusername>/<extension name>
- Verify that the changes you made a reflected in your fork of the extension
- (optional) - Make a pull request (PR) in github using github gui tools to invite primary extension owner to "pull" your changes into their master repo.
tgr's notes
[edit]You might set it something other than origin, but that's more of a personal workflow choice. e.g.:
- git remote set-url fork ...;
- git branch my-fix;
- git commit;
- git push fork;
- git checkout master
...would be more of a feature branch type workflow