-
-
Notifications
You must be signed in to change notification settings - Fork 26
👷 add upstream change detection #31
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
Conversation
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.
LGTM, although it would be good to have it open an issue when the hashes change, since it would be hard for someone to notice just by checking when the workflow fails.
SGTM if someone else wants to do the work! 😄 |
I can do it once this is merged. |
const knownWriteHeadHash = '281e0d02084a69893b8c3b8692e3c7c4de2ce22a626217fcf597fa6ddf6955a9' | ||
const knownSetHeaderHash = '2d4f95e92586d28bfd4d3137a8eaacb82b255967d8c26413015c6b56daf0afe7' | ||
const knownAppendHeaderHash = '0deb9f70c3bba63993321cca9281fb4607e2567bed1436b8574c5b86698125a8' | ||
const knownRemoveHeaderHash = '3ad5ccb0a858beb6268f281492bd8d42c9815f5316cc3c4f7f735e142fcd29d9' |
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.
Could we add some automation to update these after a change is looked into? Just to make it easier than copy pasting the new value from the failed build?
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.
sure, should be a straight-forward follow-on.
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.
An affront to g*d, but is informational and we can remove it as soon as we are forced to atone
Co-authored-by: Wes Todd <[email protected]>
… run before merging Co-authored-by: Jon Church <[email protected]>
we need to know when node makes changes to these methods
open to better ideas though! 😆