diff --git a/docs/Wiki/development/reviewing.md b/docs/Wiki/development/reviewing.md index a9d89341..cbc722dd 100644 --- a/docs/Wiki/development/reviewing.md +++ b/docs/Wiki/development/reviewing.md @@ -19,15 +19,15 @@ It's not necessary to do both when reviewing as long as you mention what you did For code review head to the _"Files changed"_ section of the PR. -![](../.gitbook/assets/review1.png) +![](/_static/wiki/review1.png) From there you can select the line(s) you want to leave a comment on. -![](../.gitbook/assets/review2.PNG) +![](/_static/wiki/review2.PNG) Type in your comment and click on _"Start a review"_. -![](../.gitbook/assets/review3.png) +![](/_static/wiki/review3.png) Note that this will **NOT** post your comment immediately! Add any remaining comments to other lines of code, then head to the _Finishing up_ section of this wiki page to see how to post your code review. @@ -47,7 +47,7 @@ The TL;DR is to test the aspect that has been changed. After you performed the testing and/or code review leave a final comment by clicking on _"Finish your review"_ on the top right of the _"Files changed"_ page of the PR. -![](../.gitbook/assets/review4.png) +![](/_static/wiki/review4.png) In your final comment make sure to mention what you did, e.g. which aspects of the change you tested for or what you considered during code review (formatting, edge cases, ...). The more detailed this part is the easier it is for other reviewers to tell which aspects they can skip during reviewing to speed up the process. diff --git a/docs/Wiki/development/testing.md b/docs/Wiki/development/testing.md index 9125453b..4c3ce812 100644 --- a/docs/Wiki/development/testing.md +++ b/docs/Wiki/development/testing.md @@ -62,11 +62,11 @@ Alternatively, compiling the PR'd code from source is also an option. For this, Click on the source branch of the PR -![](../.gitbook/assets/download-mods-pr1.png) +![](/_static/wiki/download-mods-pr1.png) Click on _"Code"_ and then on _"Download ZIP"_ -![](../.gitbook/assets/download-mods-pr2.png) +![](/_static/wiki/download-mods-pr2.png) From there copy over all the `Northstar.XXXXX` folders into your mods folder in your Titanfall2 install the same way you would manually install mods. diff --git a/docs/.gitbook/assets/download-mods-pr1.png b/docs/_static/wiki/download-mods-pr1.png similarity index 100% rename from docs/.gitbook/assets/download-mods-pr1.png rename to docs/_static/wiki/download-mods-pr1.png diff --git a/docs/.gitbook/assets/download-mods-pr2.png b/docs/_static/wiki/download-mods-pr2.png similarity index 100% rename from docs/.gitbook/assets/download-mods-pr2.png rename to docs/_static/wiki/download-mods-pr2.png diff --git a/docs/.gitbook/assets/review1.png b/docs/_static/wiki/review1.png similarity index 100% rename from docs/.gitbook/assets/review1.png rename to docs/_static/wiki/review1.png diff --git a/docs/.gitbook/assets/review2.PNG b/docs/_static/wiki/review2.PNG similarity index 100% rename from docs/.gitbook/assets/review2.PNG rename to docs/_static/wiki/review2.PNG diff --git a/docs/.gitbook/assets/review3.png b/docs/_static/wiki/review3.png similarity index 100% rename from docs/.gitbook/assets/review3.png rename to docs/_static/wiki/review3.png diff --git a/docs/.gitbook/assets/review4.png b/docs/_static/wiki/review4.png similarity index 100% rename from docs/.gitbook/assets/review4.png rename to docs/_static/wiki/review4.png diff --git a/docs/.gitbook/assets/vtol-main-window.png b/docs/_static/wiki/vtol-main-window.png similarity index 100% rename from docs/.gitbook/assets/vtol-main-window.png rename to docs/_static/wiki/vtol-main-window.png