Skip to content

Conversation

ericcrosson-bitgo
Copy link
Contributor

With this indirection, we can configure a required status check that
doesn't require updating when Node.js LTS versions change.

(The matrix version appears in the name of the
status check, this was the least-gross workaround
I could find. Peer here for some horror shows:
https://github.community/t/status-check-for-a-matrix-jobs/127354/11)

With this indirection, we can configure a required status check that
doesn't require updating when Node.js LTS versions change.

(The matrix version appears in the name of the
status check, this was the least-gross workaround
I could find. Peer here for some horror shows:
https://github.community/t/status-check-for-a-matrix-jobs/127354/11)
@ericcrosson-bitgo ericcrosson-bitgo requested a review from a team May 13, 2022 22:35
@ericcrosson-bitgo
Copy link
Contributor Author

Success! We can see in the name of the status check now that we aren't describing a numeric Node.js version:

CI / Node.js lts/* (pull_request) 

key: turbo-${{ matrix.node-version }}-${{ github.ref_name }}-${{ github.job }}-${{ github.sha }}
key:
turbo-${{ matrix.node-version }}-${{ github.ref_name }}-${{ github.job
}}-${{ github.sha }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was this an auto formatting thing? This could potentially break caching.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay this build looks like it used the intended key despite this line break being added: https://github.com/BitGo/api-ts/runs/6430577428?check_suite_focus=true#step:14:5

🤷‍♂️

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmmm yes it must have been 😰

that is oddly terrifying indeed. Maybe if we wrap the value in quotes it won't wrap?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No go, still wraps

@ericcrosson-bitgo ericcrosson-bitgo merged commit 9395074 into BitGo:master May 16, 2022
@ericcrosson-bitgo ericcrosson-bitgo deleted the rename-status-checks branch May 16, 2022 15:22
@github-actions
Copy link

🎉 This PR is included in version 1.0.0-beta.10 🎉

The release is available on npm package (@beta dist-tag)

Your semantic-release bot 📦🚀

@github-actions
Copy link

🎉 This PR is included in version 0.2.0-beta.6 🎉

The release is available on npm package (@beta dist-tag)

Your semantic-release bot 📦🚀

@github-actions
Copy link

github-actions bot commented Jun 6, 2022

🎉 This PR is included in version 0.2.0-beta.2 🎉

The release is available on npm package (@beta dist-tag)

Your semantic-release bot 📦🚀

@github-actions
Copy link

🎉 This PR is included in version 0.2.0-beta.6 🎉

The release is available on npm package (@beta dist-tag)

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

2 participants