diff options
| author | Yehonal <yehonal.azeroth@gmail.com> | 2019-02-17 21:34:28 +0100 |
|---|---|---|
| committer | Yehonal <yehonal.azeroth@gmail.com> | 2019-02-17 21:34:28 +0100 |
| commit | a3d359e1cc4f40328f898653a5cc3b9711a522e6 (patch) | |
| tree | 48d879cbdbf5e78a72ca686912ca4ac361c929c7 /docs/How-to-spot-db-struct-diff-commits.md | |
| parent | b781501462339649eac45d9d54f8dbbfb11a32db (diff) | |
| download | wiki-a3d359e1cc4f40328f898653a5cc3b9711a522e6.tar.gz wiki-a3d359e1cc4f40328f898653a5cc3b9711a522e6.tar.bz2 wiki-a3d359e1cc4f40328f898653a5cc3b9711a522e6.zip | |
Import all wiki page from old wiki (links to fix)
Diffstat (limited to 'docs/How-to-spot-db-struct-diff-commits.md')
| -rw-r--r-- | docs/How-to-spot-db-struct-diff-commits.md | 35 |
1 files changed, 35 insertions, 0 deletions
diff --git a/docs/How-to-spot-db-struct-diff-commits.md b/docs/How-to-spot-db-struct-diff-commits.md new file mode 100644 index 0000000..2fd6701 --- /dev/null +++ b/docs/How-to-spot-db-struct-diff-commits.md @@ -0,0 +1,35 @@ +**1)** Clone a [3.3.5 TrinityCore](https://github.com/TrinityCore/TrinityCore/tree/3.3.5) and open it with [Visual Studio Code](https://code.visualstudio.com/) or any other IDE that has **annotate** feature (e.g. IntellIJ and similar). + +If using Visual Studio Code, you can install the [Annotator](https://github.com/ryu1kn/vscode-annotator) plugin. + +**2)** Start from a diff, that can be any of [those](https://github.com/azerothcore/azerothcore-wotlk/milestone/3)/ + +For example: + + + +**3)** Select the name of a changed field and copy it, for example `BaseAttackTime` and look for it in Visual Studio Code + +**4)** Scroll until you find the file that changes it, for example: + + + +**5)** Press CTRL+SHIFT+P (or CMD+SHIFT+P if macOS) and type Annotator + + + +**6)** Choose "Annotate the current file...", it will open something like this: + + + +**7)** Go with the mouse over the line of the change that you want to spot the commit of + + + +**8)** Copy the commit hash and paste on: + +https://github.com/TrinityCore/TrinityCore/commit/PASTE-THE-COMMIT-HASH-HERE + +that will be the commit you were looking for. + +**IMPORTANT**: it's also useful to check the file(s) that were modified on the [latest revision](https://github.com/TrinityCore/TrinityCore/tree/3.3.5) because they could have been modified in newer commits.
\ No newline at end of file |