This repository was archived by the owner on Oct 31, 2025. It is now read-only.
forked from azerothcore/azerothcore-wotlk
-
Notifications
You must be signed in to change notification settings - Fork 4
rebase #25
Open
hatersgit
wants to merge
4,638
commits into
hatersgit:master
Choose a base branch
from
azerothcore:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
rebase #25
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Referenced commit(s): d1273bd
…evement Fa-la-la-la-Ogri'la (#24155)
Referenced commit(s): 9dab2d4
Referenced commit(s): 3be449c
Referenced commit(s): 63553ac
Referenced commit(s): cdaf865
Referenced commit(s): 3e67f33
…nd add missing gossip (#24140)
Referenced commit(s): 8b6dfff
…24124) Co-authored-by: STARRHELD <STARRHELD@users.noreply.github.com> Co-authored-by: Gultask <100873791+Gultask@users.noreply.github.com>
Referenced commit(s): fc52aa0
Co-authored-by: ariel- <ariel-@users.noreply.github.com>
Referenced commit(s): f79f3bb
Referenced commit(s): bb18f0a
Referenced commit(s): 5ef7293
Co-authored-by: FlyingArowana <TheSCREWEDSoftware@users.noreply.github.com>
Referenced commit(s): 7c98878
…it for enemy players (#24166)
…#24356) Co-authored-by: sudlud <sudlud@users.noreply.github.com> Co-authored-by: Benjamin Jackson <38561765+heyitsbench@users.noreply.github.com>
…ton and phasing for following quests (#24357) Co-authored-by: sudlud <sudlud@users.noreply.github.com>
Referenced commit(s): cb69e65
…y was on dead side for the whole fight (#24344)
Co-authored-by: sogladev <sogladev@gmail.com>
…s during Mounting Up (#24374)
Referenced commit(s): a4c2476
…affected by Ice Nova (#24354)
Co-authored-by: Degen <61268368+aradep@users.noreply.github.com>
…re hostile to your player's team. (#24100) Co-authored-by: Kitzunu <24550914+Kitzunu@users.noreply.github.com>
Co-authored-by: victor <vngodoyr@unap.cl>
Co-authored-by: Ariel Silva <ariel-@users.noreply.github.com>
Referenced commit(s): db2dafe
…nce (#24381) Co-authored-by: blinkysc <blinkysc@users.noreply.github.com>
Referenced commit(s): 9e6493f
Co-authored-by: blinkysc <blinkysc@users.noreply.github.com>
Referenced commit(s): 67f9b72
Referenced commit(s): fded8c4
Referenced commit(s): df98dc8
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes Proposed:
This PR proposes changes to:
Issues Addressed:
SOURCE:
The changes have been validated through:
Tests Performed:
This PR has been:
How to Test the Changes:
Known Issues and TODO List:
How to Test AzerothCore PRs
When a PR is ready to be tested, it will be marked as [WAITING TO BE TESTED].
You can help by testing PRs and writing your feedback here on the PR's page on GitHub. Follow the instructions here:
http://www.azerothcore.org/wiki/How-to-test-a-PR
REMEMBER: when testing a PR that changes something generic (i.e. a part of code that handles more than one specific thing), the tester should not only check that the PR does its job (e.g. fixing spell XXX) but especially check that the PR does not cause any regression (i.e. introducing new bugs).
For example: if a PR fixes spell X by changing a part of code that handles spells X, Y, and Z, we should not only test X, but we should test Y and Z as well.