Test staging - #203
Merged
Merged
Conversation
Referenced commit(s): 75d7b19
…thcore#25387) Co-authored-by: Andrew <47818697+Nyeriah@users.noreply.github.com> Co-authored-by: Ryan Turner <16946913+TheSCREWEDSoftware@users.noreply.github.com>
…e#25589) Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
…ore#25590) Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
Referenced commit(s): 504b172
…zerothcore#25568) Co-authored-by: FlyingArowana <TheSCREWEDSoftware@users.noreply.github.com> Co-authored-by: Rocco Silipo <108557877+Rorschach91@users.noreply.github.com>
Referenced commit(s): 0db7c2d
Referenced commit(s): c6c308a
Referenced commit(s): 6f31825
Referenced commit(s): bcf13e4
Referenced commit(s): ffaebac
Referenced commit(s): abbc37a
Referenced commit(s): 7ff0efa
Referenced commit(s): cf62b76
…tems (azerothcore#25563) Co-authored-by: Ryan Turner <16946913+TheSCREWEDSoftware@users.noreply.github.com>
Referenced commit(s): 7214150
…thcore#25692) Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
…thcore#25585) Co-authored-by: Gustavo <sirikfoll@hotmail.com>
…othcore#25318) Co-authored-by: blinkysc <blinkysc@users.noreply.github.com>
Referenced commit(s): 685ef83
…if they are despawning- (azerothcore#25700)
Referenced commit(s): 74a42f5
Referenced commit(s): b9a4028
Co-authored-by: Andrew <47818697+Nyeriah@users.noreply.github.com>
Referenced commit(s): c9eace6
Referenced commit(s): 1cd8516
azerothcore#25310) Co-authored-by: blinkysc <blinkysc@users.noreply.github.com>
…othcore#25709) Co-authored-by: blinkysc <blinkysc@users.noreply.github.com>
… quest Last Rites and Thassarian should even ends its move_to_pos. (azerothcore#25713) Co-authored-by: Sogladev <sogladev@gmail.com>
Referenced commit(s): e61c2c5
Referenced commit(s): 8060e15
Referenced commit(s): abddb66
…ore#25721) Co-authored-by: blinkysc <blinkysc@users.noreply.github.com>
Referenced commit(s): e4c596e
…zerothcore#25723) Co-authored-by: blinkysc <blinkysc@users.noreply.github.com>
# Conflicts: # .github/workflows/windows_build.yml
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
14 participants
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:
AI-assisted Pull Requests
Important
While the use of AI tools when preparing pull requests is not prohibited, contributors must clearly disclose when such tools have been used and specify the model involved.
Contributors are also expected to fully understand the changes they are submitting and must be able to explain and justify those changes when requested by maintainers.
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.