Remove bakery-pr job from ci.yml#449
Merged
Merged
Conversation
GitHub cannot resolve relative reusable workflow refs (./path) during pull_request validation for recently added files. This causes startup_failure on every PR. The bakery-pr test job will be re-added in the product repo rollout PRs which call bakery-build-pr.yml via the full repo path.
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
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.
Summary
Remove the
bakery-prCI job that was added in #442. GitHub cannot resolve relative reusable workflow refs ("./.github/workflows/bakery-build-pr.yml") duringpull_requestvalidation for recently added files, causingstartup_failureon every PR to the repo.The
bakery-build-pr.ymlworkflow file remains — it will be called by product repos via the full repo path (posit-dev/images-shared/.github/workflows/bakery-build-pr.yml@main) in the product repo rollout PRs (6-9 in rstudio/platform-team#435).Test plan