Skip to content

Comments

update merged performer upon batch update#5664

Merged
WithoutPants merged 4 commits intostashapp:developfrom
fume8866:feature/merged-performer
Feb 27, 2025
Merged

update merged performer upon batch update#5664
WithoutPants merged 4 commits intostashapp:developfrom
fume8866:feature/merged-performer

Conversation

@fume8866
Copy link
Contributor

Closes #5663

For consideration:

  • this logic always runs upon batch update - not sure if a user would want to disable it
  • during testing, I noticed that if the user does a batch update with the Name field excluded, this is likely to prevent the update from succeeding due to the name change being ignored and the new performer usually having an alias matching the original name.

@WithoutPants WithoutPants added the improvement Something needed tweaking. label Feb 26, 2025
@WithoutPants WithoutPants added this to the Version 0.28.0 milestone Feb 26, 2025
@WithoutPants WithoutPants merged commit 4d447c3 into stashapp:develop Feb 27, 2025
2 checks passed
XGFan pushed a commit to XGFan/stash that referenced this pull request Mar 27, 2025
* update merged performer upon batch update
* Handle aliases and name for merged performer
* Refactor merge performer code

Log when merging performers
---------
Co-authored-by: WithoutPants <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

improvement Something needed tweaking.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature] Batch update merged performers from stashbox

2 participants