-
Notifications
You must be signed in to change notification settings - Fork 53
CI: Add a comment if a PR touches sysvars #136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
#### Problem As noted at anza-xyz/agave#428 (comment), it's possible to update the Rust client and forget to update the JS client. #### Summary of changes Copy the solution at https://github.com/orgs/community/discussions/69944#discussioncomment-10796276, but adapt it to our needs. NOTE: I'll try updating some paths to see if this works.
Taking a look at https://github.com/marketplace/actions/comment-pull-request#permissions, I don't think I'll be able to properly test this, but I think the perms will be correct once we land this. I can open a test PR after this |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that synchronized
is the event type that you're looking for to test whether this puppy runs on updates, but meh; it probably works.
Thanks!
But yeah also, forks. |
Oh yeah, good call, updated to add |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Problem
As noted at
anza-xyz/agave#428 (comment), it's possible to update the Rust client and forget to update the JS client.
Summary of changes
Copy the solution at https://github.com/orgs/community/discussions/69944#discussioncomment-10796276, but adapt it to our needs.
NOTE: I'll try updating some paths to see if this works.Testing failed, oh well