You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: CHANGELOG.md
+14-1
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,20 @@ Please consider [donating](https://docs.fleaflet.dev/supporters#support-us) or [
4
4
5
5
This CHANGELOG does not include every commit and/or PR - it is a hand picked selection of the most important ones. For a full list of changes, please check the GitHub repository releases/tags.
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+12-8
Original file line number
Diff line number
Diff line change
@@ -5,11 +5,15 @@ We're always happy to receive improvements and fixes, so please submit them when
5
5
> Many feature additions are more suitable for plugins, instead of being added to the core. This is aimed to reduce the future maintenance burden/cost on the maintainers.
6
6
If we deny your PR for this reason, please do consider publishing a plugin, and we'll be happy to add it to the [Plugins List](https://docs.fleaflet.dev/plugins/list)! See [Making A Plugin](https://docs.fleaflet.dev/plugins/making-a-plugin) for more information.
7
7
8
-
***If your PR will add a major or breaking change, please discuss it with us first, via the Issue Tracker**
9
-
We don't want to waste your time if we think it's more appropriate for a plugin, and it helps to make a clear plan before starting work
10
-
***Create a draft PR as soon as work starts, and take it out of draft status when ready for review**
11
-
Keep everyone in the loop, so no-one tries working on the same thing as you
12
-
***Don't change the package version, GitHub workflows, lints, or any other meta files without clarification**
13
-
We rely on a standardized process and procedure to ensure top-quality releases
14
-
***Use a clear (preferably [Conventional](https://www.conventionalcommits.org/)) PR title**
15
-
This makes it easier for us to group commits for release and write correct CHANGELOGs
8
+
***If your PR will add a major or breaking change, please discuss it with us first, via the Issue Tracker.**
9
+
We don't want to waste your time if we think it's more appropriate for a plugin, and it helps to make a clear plan before starting work.
10
+
Additionally, if your PR makes breaking changes, or depends on another breaking commit, we may have some additional guidance.
11
+
12
+
***Create a draft PR as soon as work starts, and take it out of draft status when ready for review.**
13
+
Keep everyone in the loop, so no-one tries working on the same thing as you.
14
+
15
+
***Don't change the package version, GitHub workflows, lints, or any other meta files without clarification.**
16
+
We rely on a standardized process and procedure to ensure top-quality releases.
17
+
18
+
***Use a clear (preferably [Conventional](https://www.conventionalcommits.org/)) PR title.**
19
+
This makes it easier for us to group commits for release and write correct CHANGELOGs.
0 commit comments