Fix/quickorder inactive status message #171
Conversation
|
Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖 Please select which version do you want to release:
And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.
|
|
Beep boop 🤖 I noticed you didn't make any changes at the
In order to keep track, I'll create an issue if you decide now is not a good time
|
.vscode/settings.json
Outdated
| @@ -1,7 +1,7 @@ | |||
| { | |||
| "editor.formatOnSave": true, | |||
| "editor.codeActionsOnSave": { | |||
| "source.fixAll.eslint": true | |||
| "source.fixAll.eslint": "explicit" | |||
There was a problem hiding this comment.
probably when the file was saved, my vscode preferences changed this
Co-authored-by: ataideverton <[email protected]>
Co-authored-by: ataideverton <[email protected]>
ataideverton
force-pushed
the
fix/quickorder-inactive-status-message
branch
from
b6b3a85 to
9a8f68a
Compare
|
Your PR has been merged! App is being published. 🚀 After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:
After that your app will be updated on all accounts. For more information on the deployment process check the docs. 📖 |
What does this PR do? *
Add new message in the status column of the SKU table, specifically inactive skus
How to test it? *
Copy/Paste SkusDescribe alternatives you've considered, if any. *
Screen.Recording.2024-09-25.at.16.32.25.mov
Related to / Depends on *
Branch created from the back task