Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Adobe Exam AD0-E706 Topic 7 Question 44 Discussion

Actual exam question for Adobe's AD0-E706 exam
Question #: 44
Topic #: 7
[All AD0-E706 Questions]

You fixed an issue in a third-party extension using a patch named m2-hotfixes/extension-fix.patch Before committing the patch to the repository you want to test it locally

How do you test a patch in a clean working copy?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Zona at Sep 16, 2024, 05:23 AM

Limited Time Offer

25%

Off

Get Premium AD0-E706 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Sylvie
3 months ago
B) Run the command git apply m2-hotfixes/extension-fix.patch - Bingo! Give that person a cookie. Applying the patch before testing is the way to go. Anything else is just playing 'Magento Roulette'.
upvoted 0 times
Miles
2 months ago
B) Run the command git apply m2-hotfixes/extension-fix.patch - Bingo! Give that person a cookie. Applying the patch before testing is the way to go. Anything else is just playing 'Magento Roulette'.
upvoted 0 times
...
Titus
2 months ago
C) Run the command bin/magento setup:hotfix:apply --patch=m2-hotfixes/extension-fix.patch
upvoted 0 times
...
Karon
3 months ago
B) Run the command git apply m2-hotfixes/extension-fix.patch
upvoted 0 times
...
...
Stevie
3 months ago
D) Configure a deploy hook in .magento.app.yaml that executes - Ah, the old 'deploy it to production and see what happens' strategy. Bold move, my friend, but I prefer to test in a safe environment first.
upvoted 0 times
...
Lavonda
3 months ago
C) Run the command bin/magento setup:hotfix:apply --patch=m2-hotfixes/extension-fix.patch - Nah, that's not the right way to test a patch. I'd rather use a magic wand and hope for the best.
upvoted 0 times
...
Kallie
3 months ago
A) Commit the patch because the pre-commit hook will abort the commit if any hotfix causes an issue - Really? Committing a patch without testing it first? That's like jumping off a cliff and hoping you'll grow wings on the way down.
upvoted 0 times
Justine
2 months ago
A) Commit the patch because the pre-commit hook will abort the commit if any hotfix causes an issue - Really? Committing a patch without testing it first? That's like jumping off a cliff and hoping you'll grow wings on the way down.
upvoted 0 times
...
Cheryl
2 months ago
C) Run the command bin/magento setup:hotfix:apply --patch=m2-hotfixes/extension-fix.patch
upvoted 0 times
...
Keena
3 months ago
B) Run the command git apply m2-hotfixes/extension-fix.patch
upvoted 0 times
...
...
Gail
4 months ago
B) Run the command git apply m2-hotfixes/extension-fix.patch - This is the correct answer. We need to apply the patch before testing it locally, not commit it directly.
upvoted 0 times
Rosio
3 months ago
No need for that. Just apply the patch using git apply command.
upvoted 0 times
...
Dianne
3 months ago
Should we also consider configuring a deploy hook in .magento.app.yaml?
upvoted 0 times
...
Tomoko
3 months ago
Yes, that's correct. We need to apply the patch before testing it locally.
upvoted 0 times
...
Hester
4 months ago
I think we should run the command git apply m2-hotfixes/extension-fix.patch
upvoted 0 times
...
...
Elmira
4 months ago
I'm not sure, but maybe configuring a deploy hook in .magento.app.yaml could also work
upvoted 0 times
...
Laquita
4 months ago
I agree with Na, running the git apply command seems like the right approach
upvoted 0 times
...
Na
4 months ago
I think the correct way is to run the command git apply m2-hotfixes/extension-fix.patch
upvoted 0 times
...

Save Cancel