-
Notifications
You must be signed in to change notification settings - Fork 29.7k
add .pub-cache back to .gitignore #128894
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
add .pub-cache back to .gitignore #128894
Conversation
|
test-exempt: configuration change but bonus points for actually testing it. obviously the simple test is just literally checking the file contains what you expect, but the more elaborate test would be checking that the scenario you describe works as expected. |
I considered writing a test, but I'm not sure there would be much value. I'm not too worried about However we don't currently have infra for seeing the diff associated with the current PR (we can't check the current commit because there may be multiple commits in a PR, and the HEAD commit may not have the offending change). |
This would be difficult to do. Ideally you would download a prebuilt archive and then Also we'd have the problem of which older archive to grab. The perfect test would grab all published release archives ever and ensure they can successfully upgrade to the commit under test. |
|
Would it be worth adding a comment to the .gitignore cautioning against removing entries? (edited for typos) |
andrewkolos
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.
See previous comment (I forgot to mark it as a review)
Done |
andrewkolos
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.
LGTM with uber nit
.gitignore
Outdated
| @@ -1,3 +1,6 @@ | |||
| # Do not remove or rename entries in this file, only add new ones | |||
| # See https://github.com/flutter/flutter/issues/128635 for more context | |||
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.
| # See https://github.com/flutter/flutter/issues/128635 for more context | |
| # See https://github.com/flutter/flutter/issues/128635 for more context. |
|
auto label is removed for flutter/flutter, pr: 128894, due to - The status or check suite Google testing has failed. Please fix the issues identified (or deflake) before re-applying this label. |
Just a small correction for later context. This was not a rename:
|
Understood. I meant the effective change to the .gitignore, but I should have been more clear. |
flutter/flutter@b0188cd...fc8856e 2023-06-16 [email protected] [web] Don't crash on `const HtmlElementView()` (flutter/flutter#128965) 2023-06-16 [email protected] Roll Packages from 0507297 to f9314a3 (3 revisions) (flutter/flutter#128878) 2023-06-16 [email protected] Update getProperties to handle Diagnosticable as input. (flutter/flutter#128897) 2023-06-15 [email protected] Roll Flutter Engine from 48e0b4e66422 to fb5fed432e59 (1 revision) (flutter/flutter#128967) 2023-06-15 [email protected] Fix dart pub cache clean command on pub.dart (flutter/flutter#128171) 2023-06-15 [email protected] [flutter_tools] Migrate more integration tests to process result matcher (flutter/flutter#128737) 2023-06-15 [email protected] [flutter_tools] refactor license collector (flutter/flutter#128748) 2023-06-15 [email protected] Set Semantics.button to true for date widget (flutter/flutter#128824) 2023-06-15 [email protected] Update golden tests (flutter/flutter#128914) 2023-06-15 [email protected] Roll Flutter Engine from 9934c0de738c to 48e0b4e66422 (26 revisions) (flutter/flutter#128959) 2023-06-15 [email protected] flutter update-packages --cherry-pick-package (flutter/flutter#128917) 2023-06-15 [email protected] add .pub-cache back to .gitignore (flutter/flutter#128894) 2023-06-15 [email protected] Roll Flutter Engine from 2d8d5ecfe4a8 to 9934c0de738c (2 revisions) (flutter/flutter#128849) 2023-06-15 [email protected] flutter update-packages --force-upgrade (flutter/flutter#128908) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-packages Please CC [email protected],[email protected],[email protected] on the revert to ensure that a human is aware of the problem. To file a bug in Packages: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Fixes #128635
In 1fd84f8, we renamed the
.pub-cacheentry in the.gitignorefile to.pub-preload-cache, and ensured the packaging script was now populating that directory. However, for users who already had this directory from downloading an earlier archive but usedflutter upgradeto get the latest code, they now had a.gitignorefile that was no longer ignoring their.pub-cachedirectory.Now, when these users try to
flutter upgradeagain, the tool tries to verify if their checkout is clean, and will exit early if not directing the user to either stash or commit these changes, or doflutter upgrade --forcewhich will try to update their branch anyway (and which would succeed since there would be no git conflict). These change adds back the.pub-cacheentry to.gitignore, which won't retroactively fix broken releases, but will at least ensure if theyflutter upgrade --forceonce to get this fix, they won't need to again.