Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Make explicit the use of the parameter
GITHUB_TOKEN
when usecreate_release
#420Make explicit the use of the parameter
GITHUB_TOKEN
when usecreate_release
#420Changes from 23 commits
e41a8c4
b78a5c0
4a8d792
8946ad7
6d1e690
81d954a
15099ca
e110a41
fcacaa8
302e372
461bcd8
75c420e
76f5dcc
e95557b
2576c51
c894e5e
fb94b47
126a46c
2b049f6
738c6b0
04a1e43
4527067
9031f81
eaf6ac7
8ed0e7e
8882fbd
f41bcc7
27c20dc
6adfe25
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
github_token: …
as part of the parameters used in their call sites and will instead just rely onGITHUB_TOKEN
env var being set (e.g. this call site won't require any change for it to continue working)PS: Btw, one good news to note is that, despite those items indeed being "breaking changes" (for any call site of any of those actions that relied on
GHHELPER_ACCESS
env var instead ofGITHUB_TOKEN
, and/or for call sites ofcomment_on_pr
that usedaccess_token:
parameter explicitly), in practice I doubt that many client app relied on any of those, because most of our client apps and CI rely on theGITHUB_TOKEN
env var already (as opposed toaccess_token:
param or deprecatedGHHELPER_ACCESS
env var) to provide the token, which is something that will continue working as before.So while this is correct for those changes to be under "Breaking Changes", the good news is in practice most clients will have nothing to do to adopt it 🙂 🎉
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 just triggered CI on your PR (FYI, because you're working on a fork, CI isn't run automatically—for security reasons— like it is for usual PRs), and got a rubocop warning on this line (see here):
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 do not have access to see that buildkite link 😢
I fixed the warning, hope everything pass now 👍
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've retriggered the CI on your latest commit, let's see if CI checks go green on your PR after that 🙂
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.
Yay! Bye bye
GithubHelper#github_token!
method and the need for the helper to know or look at the env vars 🎉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.
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.