mirror of
https://github.com/flutter/flutter.git
synced 2025-06-03 00:51:18 +00:00
![]() <!-- start_original_pr_link --> Reverts: flutter/flutter#166717 <!-- end_original_pr_link --> <!-- start_initiating_author --> Initiated by: matanlurey <!-- end_initiating_author --> <!-- start_revert_reason --> Reason for reverting: Broke tree on [postsubmit](https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8718108088961866849/+/u/test:_run_suite_safari-dart2js-canvaskit-engine/stdout) <!-- end_revert_reason --> <!-- start_original_pr_author --> Original PR Author: jtmcdole <!-- end_original_pr_author --> <!-- start_reviewers --> Reviewed By: {matanlurey} <!-- end_reviewers --> <!-- start_revert_body --> This change reverts the following previous change: 1. Calculate the hash in only two places: `content_aware_hash.{ps1|sh}` 2. Call this from the workflow 3. Eventually call this from `update_engine_version.{ps1|sh}` The files of import: * `DEPS`: tracks third party dependencies related to building the engine * `engine`: all the code in the engine folder * `bin/internal/content_aware_hash.ps1`: script for calculating the hash on windows * `bin/internal/content_aware_hash.sh`: script for calculating the hash on mac/linux * `.github/workflows/content-aware-hash.yml`: github action for CI/CD hashing Tested on windows and mac: ```shell PS C:\src\flutter> C:\src\flutter\bin\internal\content_aware_hash.ps1 c24231e276e0719738e175e0622e040ad21a7012 ``` ```shell ❯ ~/src/flutter/bin/internal/content_aware_hash.sh c24231e276e0719738e175e0622e040ad21a7012 ``` <!-- end_revert_body --> Co-authored-by: auto-submit[bot] <flutter-engprod-team@google.com> |
||
---|---|---|
.. | ||
about | ||
contributing | ||
ecosystem | ||
examples | ||
infra | ||
libraries/material | ||
platforms | ||
postmortems | ||
releases | ||
roadmap | ||
tool | ||
triage | ||
wiki_archive | ||
Flutter-Self-Service-Index.md | ||
In-case-of-emergency.md | ||
README.md |
This wiki is primarily aimed at engineers building or making contributions to Flutter.
If you are new to Flutter, then you will find more general information on the Flutter project, including tutorials and samples, on our website at flutter.dev. For specific information about Flutter's APIs, consider our API reference which can be found at the api.flutter.dev.
If you want to know what we're likely to do in the future, our roadmap may be of interest.
If you intend to contribute to Flutter, welcome! You are encouraged to start with our contributor guide, which helps onboard new team members. It points to the most relevant pages on this wiki. You are also invited to join our Discord server.
Index of notable sections
- Actionable bugs, and the closing of unactionable bugs
- Breaking changes
- Cherrypick process
- Closing issues
- Dashboards
- Debugging a broken engine autoroll
- Deprecations
- Design documents
- Discord
- Engineering Philosophy
- Flaky tests
- flutter.dev is down
- Issue prioritization
- Labels
- Milestones
- Plugin compatibility policy
- Reviewing code
- RFC process
- Status of popular issues
- Style guide for Flutter repo
- Submitting code, process for
- Support levels, definitions of
- Symbolicating stack traces
- Threading in the Engine
- When will my bug be fixed?
- Security best practices