mirror of
https://github.com/ionic-team/ionic-framework.git
synced 2026-03-13 10:22:08 +08:00
ec07e70d99
The team had feedback during a sprint retro that the breaking change process documentation was a bit spread out. In particular, some team members were not clear that you need to a) update the breaking.md file and b) add the "BREAKING CHANGE" comment to the commit description. This PR adds both of these things are comments for awareness.
35 lines
1.0 KiB
Markdown
35 lines
1.0 KiB
Markdown
Issue number: resolves #
|
|
|
|
---------
|
|
|
|
<!-- Please do not submit updates to dependencies unless it fixes an issue. -->
|
|
|
|
<!-- Please try to limit your pull request to one type (bugfix, feature, etc). Submit multiple pull requests if needed. -->
|
|
|
|
## What is the current behavior?
|
|
<!-- Please describe the current behavior that you are modifying. -->
|
|
|
|
## What is the new behavior?
|
|
<!-- Please describe the behavior or changes that are being added by this PR. -->
|
|
|
|
-
|
|
-
|
|
-
|
|
|
|
## Does this introduce a breaking change?
|
|
|
|
- [ ] Yes
|
|
- [ ] No
|
|
|
|
<!--
|
|
If this introduces a breaking change:
|
|
1. Describe the impact and migration path for existing applications below.
|
|
2. Update the BREAKING.md file with the breaking change.
|
|
3. Add "BREAKING CHANGE: [...]" to the commit description when merging. See https://github.com/ionic-team/ionic-framework/blob/main/.github/CONTRIBUTING.md#footer for more information.
|
|
-->
|
|
|
|
|
|
## Other information
|
|
|
|
<!-- Any other information that is important to this PR such as screenshots of how the component looks before and after the change. -->
|