###### tags: `MetaVerde` `git`
# Steps to pushing to metagame wiki repo

1. `rm -rf metagame-wiki` on your local machine
2. Go to your forked repo on github and get the clone code
3. `git clone <the url github gives you>`
4. `cd metagame-wiki`
5. `yarn`
6. This is where you might get local mumbo jumbo complainy things about updating, this is where we messed up last time and somehow bumped the version of docusaurus when updating the nvm or node or whatever.
7. Hopefully they wont complain
8. `git checkout -b new-branch`
9. make your changes:
- docs/great-houses/house-of-dapps.md
- Uncomment the house-of-dapps code
10. `git add .`
11. `git commit -m 'my commit message'`
12. `git push`
13. It will complain about set origin bla bla, copy that line and paste it
14. The successful push will produce a link to the new PR, click it in the terminal.
15. Create the PR in github UI, leave nice description and assign a reviewer.

## If stuck

- "Timebox" it, try to figure it out for 10 minutes by googling and pounding the wall, sometimes it works. Talking to yourself or a rubber duck helps too. Your spouse never wants to hear it tho, I've tried that technique too.
- Write out the problem, so someone can align with your issue without being there or in the moment, sometimes this in itself will answer your question.
- Dont worry have fun

## Some git commands

Note: I'm not using the exact correct verbage in my explainations, but they should serve as good enough for our purposes.

git fetch ## fetch the new branches that might have been created

git pull origin master --rebase ## pull from the origin repo

git add . ## add files that have been modified to tracking

git commit -m 'commit message' ## commit aka stage the files (get them ready to push)

git push ## send the files up to the parent repo (github)

## Errors

https://stackoverflow.com/questions/53471063/yarn-error-there-are-no-scenarios-must-have-at-least-one