Repository navigation
추천 카드의 임시 스타일명 39개를 실제 헤어스타일명으로 수정 - #194
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Recommendation cards still show placeholder labels such as 롱 스타일 26 and 미디엄 스타일 09/03 for 39 retained catalogue photos. Rename those reviewed active SYSTEM assets to names describing the visible hairstyle (for example 내추럴 롱 웨이브, 사이드파트 웨이브 and 슬릭백 웨이브) and align files.file_name.
Guard each update by asset ID, original label, reviewed thumbnail ID, active status and SYSTEM ownership. Preserve S3 object keys, asset IDs, recommendation profiles and historical references. Bump asset_version so cached recommendations refresh after deployment. Names describe visible shapes without asserting unverified chemical procedures.
Validated against a local copy of all 150 production catalogue records: exactly 39 labels/file names change, 111 other assets and all profiles/object keys remain unchanged, active count stays 92, and repeat execution is a no-op. Deployment uses the existing GitHub Actions/Flyway path.