ci: linkage monitor CI update to stop using .kokoro/linkage-monitor.sh #1718
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.
For #1717 ("ci / linkage-monitor" is failing), this change by synthtool expects the ci.yaml
to use the Linkage Monitor GitHub Actions and it deletes .kokoro/linkage-monitor.sh.
However this repository excludes ci.yaml from being managed by synthtool. Therefore we need to manually maintain ci.yaml to stop using linkage-monitor.sh.
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> ☕️