Update old wiki links (#149544)

Part of flutter/flutter#145009

Finishes updating links in the repo that pointed to the old wiki

Author: Piinks

.github/ISSUE_TEMPLATE/7_cherry_pick.yml

@@ -38,7 +38,7 @@ body:
       label: Changelog Description
       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
     validations:
       required: true
   - type: input

.github/ISSUE_TEMPLATE/8_design_doc.yml

@@ -8,7 +8,7 @@ body:
         Thank you for your interest in contributing to Flutter!
 
         Please ensure that you are following
-        https://github.com/flutter/flutter/wiki/Design-Documents
+        https://github.com/flutter/flutter/blob/main/docs/contributing/Design-Documents.md
         when sharing a design document.
 
         Please fill out the sections below to the best of your ability.

.github/PR_TEMPLATE/PULL_REQUEST_CP_TEMPLATE.md

@@ -1,4 +1,4 @@
-This pull request is created by [automatic cherry pick workflow](https://github.com/flutter/flutter/wiki/Flutter-Cherrypick-Process#automatically-creates-a-cherry-pick-request)
+This pull request is created by [automatic cherry pick workflow](https://github.com/flutter/flutter/blob/main/docs/releases/Flutter-Cherrypick-Process.md#automatically-creates-a-cherry-pick-request)
 Please fill in the form below, and a flutter domain expert will evaluate this cherry pick request.
 
 ### Issue Link:
@@ -7,7 +7,7 @@ What is the link to the issue this cherry-pick is addressing?
 < Replace with issue link here >
 
 ### Changelog Description:
-Explain this cherry pick in one line that is accessible to most Flutter developers. See [best practices](https://github.com/flutter/flutter/wiki/Hotfix-Documentation-Best-Practices) for examples
+Explain this cherry pick in one line that is accessible to most Flutter developers. See [best practices](https://github.com/flutter/flutter/blob/main/docs/releases/Hotfix-Documentation-Best-Practices.md) for examples
 
 < Replace with changelog description here >
 

.github/PULL_REQUEST_TEMPLATE.md

@@ -19,13 +19,13 @@
 If you need help, consider asking for advice on the #hackers-new channel on [Discord].
 
 <!-- Links -->
-[Contributor Guide]: https://github.com/flutter/flutter/wiki/Tree-hygiene#overview
-[Tree Hygiene]: https://github.com/flutter/flutter/wiki/Tree-hygiene
-[test-exempt]: https://github.com/flutter/flutter/wiki/Tree-hygiene#tests
-[Flutter Style Guide]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo
-[Features we expect every widget to implement]: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo#features-we-expect-every-widget-to-implement
+[Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview
+[Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md
+[test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests
+[Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md
+[Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement
 [CLA]: https://cla.developers.google.com/
 [flutter/tests]: https://github.com/flutter/tests
-[breaking change policy]: https://github.com/flutter/flutter/wiki/Tree-hygiene#handling-breaking-changes
-[Discord]: https://github.com/flutter/flutter/wiki/Chat
-[Data Driven Fixes]: https://github.com/flutter/flutter/wiki/Data-driven-Fixes
+[breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes
+[Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md
+[Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md

.github/workflows/easy-cp.yml

@@ -81,7 +81,7 @@ jobs:
         if: ${{ failure() && steps.attempt-cp.conclusion == 'failure' }}
         run: |
           FAILURE_MSG="Failed to create CP due to merge conflicts.<br>"
-          FAILURE_MSG+="You will need to create the PR manually. See [the cherrypick wiki](https://github.com/flutter/flutter/wiki/Flutter-Cherrypick-Process) for more info."
+          FAILURE_MSG+="You will need to create the PR manually. See [the cherrypick wiki](https://github.com/flutter/flutter/blob/main/docs/releases/Flutter-Cherrypick-Process.md) for more info."
           gh pr comment ${{ github.event.pull_request.number }} -R flutter/flutter -b "${FAILURE_MSG}"
         env:
           GITHUB_TOKEN: ${{ secrets.FLUTTERACTIONSBOT_CP_TOKEN }}

CODE_OF_CONDUCT.md

@@ -38,8 +38,7 @@ concerns. Be wary of agreement by compromise, where two good competing
 solutions are merged into one mediocre solution. A conflict is
 addressed when the participants agree that the final solution is
 _better_ than all the conflicting proposals. Sometimes the solution is
-more work than either of the proposals. [Embrace the yak
-shave](https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo#lazy-programming).
+more work than either of the proposals. [Embrace the yak shave](./docs/contributing/Style-guide-for-Flutter-repo.md#lazy-programming).
 
 ## Questions
 

CONTRIBUTING.md

@@ -3,7 +3,7 @@
 Contributing to Flutter
 =======================
 
-_tl;dr: join [Discord](https://github.com/flutter/flutter/wiki/Chat), be [courteous](CODE_OF_CONDUCT.md), follow the steps below to set up a development environment; if you stick around and contribute, you can [join the team](https://github.com/flutter/flutter/wiki/Contributor-access) and get commit access._
+_tl;dr: join [Discord](./docs/contributing/Chat.md), be [courteous](CODE_OF_CONDUCT.md), follow the steps below to set up a development environment; if you stick around and contribute, you can [join the team](./docs/contributing/Contributor-access.md) and get commit access._
 
 Welcome
 -------
@@ -17,10 +17,10 @@ doing outreach about Flutter, or helping out in any other way.
 We grant commit access (which includes full rights to the issue
 database, such as being able to edit labels) to people who have gained
 our trust and demonstrated a commitment to Flutter. For more details
-see the [Contributor access](https://github.com/flutter/flutter/wiki/Contributor-access)
-page on our wiki.
+see the [Contributor access](./docs/contributing/Contributor-access.md)
+page in our docs.
 
-We communicate primarily over GitHub and [Discord](https://github.com/flutter/flutter/wiki/Chat).
+We communicate primarily over GitHub and [Discord](./docs/contributing/Chat.md).
 
 Before you get started, we encourage you to read these documents which describe some of our community norms:
 
@@ -29,7 +29,7 @@ Before you get started, we encourage you to read these documents which describe
    also documents our conflict resolution policy and encourages people
    to ask questions.
 
-2. [Values](https://github.com/flutter/flutter/wiki/Values),
+2. [Values](./docs/about/Values.md),
    which talks about what we care most about.
 
 Helping out in the issue database
@@ -41,27 +41,27 @@ useful for our engineers.
 
 If you want to help us triage, you are very welcome to do so!
 
-1. Join the #hackers-triage [Discord channel](https://github.com/flutter/flutter/wiki/Chat).
+1. Join the #hackers-triage [Discord channel](./docs/contributing/Chat.md).
 
 2. Read [our code of conduct](CODE_OF_CONDUCT.md), which stipulates explicitly
    that everyone must be gracious, respectful, and professional. If you're helping out
    with triage, you are representing the Flutter team, and so you want to make sure to
    make a good impression!
 
-3. Help out as described in our wiki: https://github.com/flutter/flutter/wiki/Triage
+3. Help out as described in our [triage guide](./docs/triage/README.md)
    You won't be able to add labels at first, so instead start by trying to
    do the other steps, e.g. trying to reproduce the problem and asking for people to
    provide enough details that you can reproduce the problem, pointing out duplicates,
    and so on. Chat on the #hackers-triage channel to let us know what you're up to!
 
 4. Familiarize yourself with our
-   [issue hygiene](https://github.com/flutter/flutter/wiki/Issue-hygiene) wiki page,
+   [issue hygiene](./docs/contributing/issue_hygiene/README.md) wiki page,
    which covers the meanings of some important GitHub labels and
    milestones.
 
 5. Once you've been doing this for a while, someone will invite you to the flutter-hackers
    team on GitHub and you'll be able to add labels too. See the
-   [contributor access](https://github.com/flutter/flutter/wiki/Contributor-access) wiki
+   [contributor access](./docs/contributing/Contributor-access.md) wiki
    page for details.
 
 
@@ -75,9 +75,9 @@ that increase our test coverage, writing tests for issues others have filed, all
 are really valuable contributions to open source projects.
 
 If this interests you, you can jump in and submit bug reports without needing anyone's permission!
-The #quality-assurance channel on our [Discord server](https://github.com/flutter/flutter/wiki/Chat)
+The #quality-assurance channel on our [Discord server](./docs/contributing/Chat.md)
 is a good place to talk about what you're doing. We're especially eager for QA testing when
-we announce a beta release. See https://github.com/flutter/flutter/wiki/Quality-Assurance for
+we announce a beta release. See [quality assurance](./docs/releases/Quality-Assurance.md) for
 more details.
 
 If you want to contribute test cases, you can also submit PRs. See the next section
@@ -101,35 +101,35 @@ that describe these methodologies. The following list is ordered: you
 are strongly recommended to go through these documents in the order
 presented.
 
-1. [Setting up your engine development environment](https://github.com/flutter/flutter/wiki/Setting-up-the-Engine-development-environment),
+1. [Setting up your engine development environment](./docs/engine/contributing/Setting-up-the-Engine-development-environment.md),
    which describes the steps you need to configure your computer to
    work on Flutter's engine. If you only want to write code for the
    Flutter framework, you can skip this step. Flutter's engine mainly
    uses C++, Java, and Objective-C.
 
-2. [Setting up your framework development environment](https://github.com/flutter/flutter/wiki/Setting-up-the-Framework-development-environment),
+2. [Setting up your framework development environment](./docs/contributing/Setting-up-the-Framework-development-environment.md),
    which describes the steps you need to configure your computer to
    work on Flutter's framework. Flutter's framework mainly uses Dart.
 
-3. [Tree hygiene](https://github.com/flutter/flutter/wiki/Tree-hygiene),
+3. [Tree hygiene](./docs/contributing/Tree-hygiene.md),
    which covers how to land a PR, how to do code review, how to
    handle breaking changes, how to handle regressions, and how to
    handle post-commit test failures.
 
-4. [Our style guide](https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo),
+4. [Our style guide](./docs/contributing/Style-guide-for-Flutter-repo.md),
    which includes advice for designing APIs for Flutter, and how to
    format code in the framework.
 
 5. [Flutter design doc template](https://flutter.dev/go/template),
    which should be used when proposing a new technical design.  This is a good
    practice to do before coding more intricate changes.
-   See also our [guidance for writing design docs](https://github.com/flutter/flutter/wiki/Design-Documents).
+   See also our [guidance for writing design docs](./docs/contributing/Design-Documents.md).
 
 [![How to contribute to Flutter](https://img.youtube.com/vi/4yBgOBAOx_A/0.jpg)](https://www.youtube.com/watch?v=4yBgOBAOx_A)
 
 In addition to the documents, there is a video linked above on **How to contribute to Flutter**
 from the [Flutter](https://youtube.com/c/flutterdev) YouTube channel,
-there are many pages on [our Wiki](https://github.com/flutter/flutter/wiki/),
+there are many pages in [our docs](./docs/README.md),
 and an article [Contributing to Flutter: Getting Started](https://medium.com/@ayushbherwani/contributing-to-flutter-getting-started-a0db68cbcd5b)
 on Medium that may be of interest. For a curated list of pages see the sidebar
 on the wiki's home page. They are more or less listed in order of importance.
@@ -152,7 +152,7 @@ whether advocating for Flutter, answering questions in fora like
 or [Reddit](https://www.reddit.com/r/flutterhelp/new/?f=flair_name%3A%22OPEN%22),
 or creating content for our [documentation](https://docs.flutter.dev/)
 or sites like [YouTube](https://www.youtube.com/results?search_query=flutter&sp=EgQIAxAB),
-the best starting point is to join the #hackers-devrel [Discord channel](https://github.com/flutter/flutter/wiki/Chat).
+the best starting point is to join the #hackers-devrel [Discord channel](./docs/contributing/Chat.md).
 From there, you can describe what you're interested in doing, and go ahead and do it!
 As others become familiar with your work, they may have feedback, be interested in
 collaborating, or want to coordinate their efforts with yours.
@@ -162,12 +162,12 @@ API documentation
 -----------------
 
 Another great area to contribute in is sample code and API documentation. If this is an area that interests you, join our
-[Discord](https://github.com/flutter/flutter/wiki/Chat) server and introduce yourself on the #hackers-deverl, #hackers-framework,
+[Discord](./docs/contributing/Chat.md) server and introduce yourself on the #hackers-deverl, #hackers-framework,
 or #hackers-engine channels, describing your area of interest. As our API docs are integrated into our source code, see the
 "developing for Flutter" section above for a guide on how to set up your developer environment.
 
 To contribute API documentation, an excellent command of the English language is particularly helpful, as is a careful attention to detail.
-We have a [whole section in our style guide](https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo#documentation-dartdocs-javadocs-etc)
+We have a [whole section in our style guide](./docs/contributing/Style-guide-for-Flutter-repo.md#documentation-dartdocs-javadocs-etc)
 that you should read before you write API documentation. It includes notes on the "Flutter Voice", such as our word and grammar conventions.
 
 In general, a really productive way to improve documentation is to use Flutter and stop any time you have a question: find the answer, then
@@ -186,13 +186,13 @@ Releases
 
 If you are interested in participating in our release process, which may involve writing release notes and blog posts, coordinating the actual
 generation of binaries, updating our release tooling, and other work of that nature, then reach out on the #hackers-releases
-channel of our [Discord](https://github.com/flutter/flutter/wiki/Chat) server.
+channel of our [Discord](./docs/contributing/Chat.md) server.
 
 
 Social events in the contributor community
 ------------------------------------------
 
 Finally, one area where you could have a lot of impact is in contributing to social interactions among the Flutter contributor community itself.
 This could take the form of organizing weekly video chats on our Discord, or planning tech talks from contributors, for example.
-If this is an area that is of interest to you, please join our [Discord](https://github.com/flutter/flutter/wiki/Chat) and ping Hixie on the #hackers
+If this is an area that is of interest to you, please join our [Discord](./docs/contributing/Chat.md) and ping Hixie on the #hackers
 channel!

README.md

@@ -24,7 +24,7 @@ open source.
 
 * [Install Flutter](https://flutter.dev/get-started/)
 * [Flutter documentation](https://docs.flutter.dev/)
-* [Development wiki](https://github.com/flutter/flutter/wiki)
+* [Development wiki](./docs/README.md)
 * [Contributing to Flutter](https://github.com/flutter/flutter/blob/main/CONTRIBUTING.md)
 
 For announcements about new releases, follow the
@@ -100,7 +100,7 @@ Information on how to get started can be found in our
 [contributor guide](CONTRIBUTING.md).
 
 [flutter.dev]: https://flutter.dev
-[Discord instructions]: https://github.com/flutter/flutter/wiki/Chat
+[Discord instructions]: ./docs/contributing/Chat.md
 [Discord badge]: https://img.shields.io/discord/608014603317936148?logo=discord
 [Twitter handle]: https://img.shields.io/twitter/follow/flutterdev.svg?style=social&label=Follow
 [Twitter badge]: https://twitter.com/intent/follow?screen_name=flutterdev

analysis_options.yaml

@@ -158,7 +158,7 @@ linter:
     # - prefer_constructors_over_static_methods # far too many false positives
     - prefer_contains
     # - prefer_double_quotes # opposite of prefer_single_quotes
-    # - prefer_expression_function_bodies # conflicts with https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo#consider-using--for-short-functions-and-methods
+    # - prefer_expression_function_bodies # conflicts with ./docs/contributing/Style-guide-for-Flutter-repo.md#consider-using--for-short-functions-and-methods
     - prefer_final_fields
     - prefer_final_in_for_each
     - prefer_final_locals
@@ -171,7 +171,7 @@ linter:
     - prefer_if_null_operators
     - prefer_initializing_formals
     - prefer_inlined_adds
-    # - prefer_int_literals # conflicts with https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo#use-double-literals-for-double-constants
+    # - prefer_int_literals # conflicts with ./docs/contributing/Style-guide-for-Flutter-repo.md#use-double-literals-for-double-constants
     - prefer_interpolation_to_compose_strings
     - prefer_is_empty
     - prefer_is_not_empty

dev/bots/README.md

@@ -10,7 +10,7 @@ Flutter build results are available at:
 
 Flutter infra requires special permissions to retrigger builds on the
 [build dashboard](https://flutter-dashboard.appspot.com/#/build). File an
-[infra ticket](https://github.com/flutter/flutter/wiki/Infra-Ticket-Queue) to
+[infra ticket](../../docs/infra/Infra-Ticket-Queue.md) to
 request permission.
 
 The [Cirrus](https://cirrus-ci.org)-based bots run the [`test.dart`](test.dart)
@@ -28,7 +28,7 @@ The build dashboard includes post-commit testing run on physical devices. See
 A [set of infra scripts](https://flutter.googlesource.com/recipes/)
 run on Windows, Linux, and Mac machines. The configuration for how many
 machines and what kind are managed internally by Google. File an
-[infra ticket](https://github.com/flutter/flutter/wiki/Infra-Ticket-Queue)
+[infra ticket](../../docs/infra/Infra-Ticket-Queue.md)
 to request new machine types to be added. Both of these technologies are highly
 specific to the [LUCI](https://github.com/luci) project, which is the successor
 to Chromium's infra and the foundation to Flutter's infrastructure.