-
Notifications
You must be signed in to change notification settings - Fork 260
chore(dev): static api analysis #6159
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
base: main
Are you sure you want to change the base?
Conversation
|
…g api change reports and requiring additional approval if needed
93ffb4a
to
f5f5157
Compare
|
|
… assuming we are at the root of the repo
|
|
|
|
|
|
|
|
…and look specifically for the text that tells us if anything changed
|
…ter sdk on workflow but need to see how to get the latest version automatically
…nsistency from local to gh actions
…flow instead of comparing diffs
…into chore/api-analysis
packages/aft/lib/src/commands/generate/generate_api_report_command.dart
Outdated
Show resolved
Hide resolved
packages/aft/lib/src/commands/generate/generate_api_report_command.dart
Outdated
Show resolved
Hide resolved
packages/aft/lib/src/commands/generate/generate_api_report_command.dart
Outdated
Show resolved
Hide resolved
packages/aft/lib/src/commands/generate/generate_api_report_command.dart
Outdated
Show resolved
Hide resolved
…e for parsing pubspecs
…have consistent ordering when viewing change reports
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.
Can you update the AFT ReadMe to reference this new command.
…its example subdirectory
…se of API change reporting
Issue #, if available:
Description of changes:
Introduced the
aft generate api-report
command to AFT. This command uses dart_apitool from @bmw-tech to create snapshots of our package's dart level API surfaces, and a change report for these. Developers must now always use this AFT command to generate these files for each package (just running the command as is once here works) on every Pull Request that is expected to merge into main.This PR also includes a workflow for checking that these change reports are actually updated according to the changes on the PR branch, and a workflow for requiring additional approvals when an API change actually occurs (as shown by the lovely bot in this thread).
Overall this change to our development flow will enforce that developers are always aware of API changes to help us get the right eyes on it and to help with versioning.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.