// Prepare a pull request by running presubmit with fixes. Use when preparing to commit or send a PR.
| name | preparing-pr |
| description | Prepare a pull request by running presubmit with fixes. Use when preparing to commit or send a PR. |
Follow these steps to prepare a pull request for DevTools:
dt configuration:
dt is available on the path by running dt --help or verifying its alias.dt executable on your path.dt update-flutter-sdk to ensure the SDK is up to date.dt presubmit --fix to address automated fixes.dt presubmit --fix again to verify the fix.git status or git diff upstream/master to find changed files.packages/devtools_app/lib/src/screens/logging/logging_screen.dart, run the logging tests under packages/devtools_app/test/screens/logging/.If any step fails, stop and address the issue, and then verify the issue is fixed before proceeding.
[!IMPORTANT] Do NOT commit or push changes without getting explicit user approval first.
Find and close obsolete, stale, or not reproducible issues in the flutter/devtools repository.
Use when documenting changes in CHANGELOG.md files for devtools_shared, devtools_app_shared, or devtools_extensions.
Guides updating dependency versions in published packages to avoid mono-repo resolution failures.
Adds copyright headers to files based on file type. Use when creating new files or when asked to verify copyright headers.
Adds user-facing change descriptions to DevTools release notes. Use when documenting improvements, fixes, or new features in the NEXT_RELEASE_NOTES.md file.
Guides the creation of high-quality, effective skills for agentic workflows. Use when creating or modifying skills in the .agents/skills/ directory.