How can I edit PKGBUILDs with the new yay?

[mihalycsaba]

Affected Version

yay -V
yay v12.0.2 - libalpm v13.0.2

Describe the bug

I have this in my config.json “editmenu”: true, but looks like the yay skips the edit question.

Reproduction Steps

[csaba@csaba-mini ~]$ yay
[sudo] password for csaba: 
:: Synchronizing package databases...
 endeavouros is up to date
 core is up to date
 extra is up to date
 community is up to date
 multilib is up to date
:: Searching AUR for updates...
:: Searching databases for updates...
:: 2 Packages to upgrade.
2  aur/proton-ge-custom  2:GE.Proton7.53-1 -> 2:GE.Proton7.54-1
1  aur/wine-ge-custom    1:GE.Proton7.41-1 -> 1:GE.Proton7.42-1
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)
 -> May cause partial upgrades and break systems
==> 1
AUR Explicit (1): proton-ge-custom-2:GE.Proton7.54-1
:: (1/1) Downloaded PKGBUILD: proton-ge-custom
==> Making package: proton-ge-custom 2:GE.Proton7.54-1 (Tue 04 Apr 2023 09:18:50 PM EEST)
==> Retrieving sources...
  -> Cloning proton-ge-custom git repo...
Cloning into bare repository '/home/csaba/.cache/yay/proton-ge-custom/proton-ge-custom'...
remote: Enumerating objects: 23274, done.
remote: Counting objects: 100% (55/55), done.
remote: Compressing objects: 100% (30/30), done.

Expected behavior

Ask if I want to edit the PKGBUILD, like it did before.

[Jguer]

Yay would still propose you to edit it after (and changes would be taken into account) but as stated in #2071 no makepkg action should be done until the user has either used diff/edit on the repo.

Thanks for raising this issue, yay-git should contain the fix if you want to test