-
Notifications
You must be signed in to change notification settings - Fork 333
[Full] bump go to 1.16 #350
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
csweichel
left a comment
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.
Thanks. Change LGTM.
|
Many thanks for this upgrade @gengjiawen! And thanks @csweichel for merging! However, in the future, please don't merge PRs like these without first:
For example, merging this Pull Request broke the build. The logged error is: |
Can this be auto for PRs ? |
That's a great point. It's currently disabled for Pull Requests from forks, because the CircleCI configuration cannot be shared with forks for security reasons. That's why our process for triggering CircleCI builds on Pull Requests from forks is basically "check out the fork, push to a new branch under upstream" (which triggers a CircleCI build, and even shows the results in the PR because the commit SHA is identical). There is a similar situation for Pull Requests against https://github.com/gitpod-io/gitpod, but there the process is simpler (someone with write access can simply comment "/werft run" on the PR and a bot triggers the build). Maybe we should add a similar comment-triggered CI bot here? |
PTAL #352 |
No description provided.