run all CI on Gemfile or Gemfile.lock change#6857
Merged
jakecoffman merged 5 commits intomainfrom Mar 17, 2023
Merged
Conversation
Nishnha
approved these changes
Mar 16, 2023
Member
|
The filters managed by this action: https://github.com/dorny/paths-filter Not sure if the |
pavera
approved these changes
Mar 16, 2023
c84d558 to
f98da5a
Compare
Member
|
Rebased the branch so it includes the changes from #6855 |
1 task
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.
One of our tests starting failing out of nowhere and slowed us down a bit. We found this was due to a fairly minor Octokit change in #6826.
To catch this sort of thing sooner, we should be running all CI whenever the updater Gemfile or lock changes.
I wasn't sure if
updater/Gemfile*would pick up both, so I opted forupdater/Gemfil*.