ci: removing Kokoro settings that are covered by GitHub Actions #1273
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
google-cla
bot
added
the
cla: yes
suztomo
changed the title
suztomo
commented
Feb 22, 2021
.github/sync-repo-settings.yaml
Outdated
Comment on lines
31
to
37
| - "units (7)" | ||
| - "units (8)" | ||
| - "units (11)" | ||
| - "windows" | ||
| - "linkage-monitor" | ||
| - "lint" | ||
| - "clirr" |
There was a problem hiding this comment.
These are checks that are already green. The "dependencies" are still red.
chingor13
approved these changes
Feb 23, 2021
|
@chingor13 Thank you for the advice. Now all Kokoro lines are removed. I'll merge this once the checks pass. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The GitHub Actions have been enabled in this repository. I believe we no longer need the Kokoro builds here.
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes #<issue_number_goes_here> ☕️