-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Update old wiki links #149544
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
Update old wiki links #149544
Conversation
docs/contributing/testing/Writing-a-golden-file-test-for-package-flutter.md
Outdated
Show resolved
Hide resolved
packages/flutter_tools/test/commands.shard/permeable/create_test.dart
Outdated
Show resolved
Hide resolved
dev/bots/test/analyze-test-input/root/packages/foo/bad_repository_links.dart
Outdated
Show resolved
Hide resolved
This comment was marked as outdated.
This comment was marked as outdated.
stuartmorgan-g
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, but one question about main vs master.
| description: >- | ||
| Explain this CP in less than 80 characters that is accessible to most Flutter developers | ||
| See https://github.com/flutter/flutter/wiki/Hotfix-Documentation-Best-Practices for examples | ||
| See https://github.com/flutter/flutter/blob/main/docs/releases/Hotfix-Documentation-Best-Practices.md for examples |
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.
Do we really want to link to main everywhere? Don't edits still have to be made to master, making it harder to edit if we link to main?
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.
Yeah, this really annoyed me. I feel like if we put main, we're more likely to get PRs opened against main.
However, our analyzer script (only in flutter/flutter) enforces using main and does not allow master.
When I first put up this PR is was all master, and then I changed it to main to make CI happy. We don't do it that other repos. It feels like a footgun for contributors. 🤷
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.
Weird! Hopefully our bot that changes branch targets will auto-fix that when people open PRs.
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.
However, our analyzer script (only in flutter/flutter) enforces using main and does not allow master.
Can we change the script instead?
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.
However, our analyzer script (only in flutter/flutter) enforces using main and does not allow master.
Can we change the script instead?
Oh can we? It looks like it's fairly recent, added in #146882 as part of #121564. But if that issue is not actively being worked on, maybe we can revert this analyzer bit.
There is already quite a list of exempt repos.. because they don't have a main branch.
Lines 1303 to 1320 in a92318d
| const Set<String> repoExceptions = <String>{ | |
| 'bdero/flutter-gpu-examples', | |
| 'chromium/chromium', | |
| 'clojure/clojure', | |
| 'dart-lang/test', // TODO(guidezpl): remove when https://github.com/dart-lang/test/issues/2209 is closed | |
| 'dart-lang/webdev', | |
| 'eseidelGoogle/bezier_perf', | |
| 'flutter/devtools', // TODO(guidezpl): remove when https://github.com/flutter/devtools/issues/7551 is closed | |
| 'flutter/flutter_gallery_assets', // TODO(guidezpl): remove when subtask in https://github.com/flutter/flutter/issues/121564 is complete | |
| 'flutter/flutter-intellij', // TODO(guidezpl): remove when https://github.com/flutter/flutter-intellij/issues/7342 is closed | |
| 'flutter/platform_tests', // TODO(guidezpl): remove when subtask in https://github.com/flutter/flutter/issues/121564 is complete | |
| 'flutter/web_installers', | |
| 'glfw/glfw', | |
| 'GoogleCloudPlatform/artifact-registry-maven-tools', | |
| 'material-components/material-components-android', // TODO(guidezpl): remove when https://github.com/material-components/material-components-android/issues/4144 is closed | |
| 'torvalds/linux', | |
| 'tpn/winsdk-10', | |
| }; |
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.
Lemme take a look
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.
Added 'flutter/flutter' with a TODO and link to the tracking issue, which is currently unassigned
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.
Circling back on this, I won't change all of the instance of main in this PR, since that will put us in a mixed state with all the other main links we previously enforced. I'll send another PR that switches all instances back to master if that is what we'd like to do.
|
auto label is removed for flutter/flutter/149544, due to - The status or check suite Mac_arm64 framework_tests_misc has failed. Please fix the issues identified (or deflake) before re-applying this label. |
|
auto label is removed for flutter/flutter/149544, due to - The status or check suite Google testing has failed. Please fix the issues identified (or deflake) before re-applying this label. |
flutter/flutter@5187cab...ccf3abe 2024-06-17 [email protected] Roll Flutter Engine from 2218a4566765 to 5989f0215fed (9 revisions) (flutter/flutter#150373) 2024-06-17 [email protected] Update API docs footer (flutter/flutter#150347) 2024-06-17 [email protected] Update old wiki links (flutter/flutter#149544) 2024-06-17 [email protected] Fix flaky complex_layout_scroll_perf__memory & flutter_gallery__memory_nav (flutter/flutter#150368) 2024-06-17 [email protected] Roll Packages from dd04ab1 to 711b4ac (3 revisions) (flutter/flutter#150359) 2024-06-17 [email protected] Roll Flutter Engine from 9779c273aac3 to 2218a4566765 (3 revisions) (flutter/flutter#150298) 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] 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://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Part of #145009
Finishes updating links in the repo that pointed to the old wiki
Pre-launch Checklist
///).If you need help, consider asking for advice on the #hackers-new channel on Discord.