Skip to content

Match on PIdnUseExp instead of PIdnUse#908

Merged
rayman2000 merged 4 commits intoviperproject:masterfrom
LaurenzV:test-fix
Mar 17, 2025
Merged

Match on PIdnUseExp instead of PIdnUse#908
rayman2000 merged 4 commits intoviperproject:masterfrom
LaurenzV:test-fix

Conversation

@LaurenzV
Copy link
Contributor

Necessary for viperproject/silver#820.

@rayman2000 rayman2000 merged commit 202cfa3 into viperproject:master Mar 17, 2025
2 checks passed
@LaurenzV
Copy link
Contributor Author

I'm not sure what's going on, but now it fails even earlier when checking out the branch: https://github.com/viperproject/silver/actions/runs/13896191787/job/38877256432?pr=820 😅 I'm not sure why, but I presume my merge commit from main somehow trips it up when trying to check out silver now... I presume the PR should have been squashed before merging, any idea how to fix?

@rayman2000
Copy link
Contributor

Hmm not sure if we can easily remove commits, we have branch protection on. Reverting the changes in a new commit will not solve this problem right?

@LaurenzV
Copy link
Contributor Author

I think not, but I'm also not sure what exactly the problem is, because the submodule still seems to link to viperproject/silver... Is it somehow possible to manually trigger a update submodules from Silver Bot?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants