Skip to content

Commit 965d08e

Browse files
authored
Good practices (#15)
Description of some good practices for develooping plugins.
1 parent eb477f6 commit 965d08e

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

README.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,18 @@ _* This is just my own eperience. Git Extensions follow SemVer, but it's public
2525

2626
### Plugin.cs
2727
- Nothing special, but ordinary Git Extensions plugin :-)
28+
29+
## Good practices
30+
31+
Here are some advices that we learned over the time.
32+
33+
### Always target single Git Extensions version
34+
35+
Until Git Extensions provides a stable API for developing plugins, most of the plugins must use un stable API that may change in every Git Extensions version. So it is good to always target single version when defining a package reference on `GitExtensions.Extensibility`.
36+
37+
### Follow semantic versioning
38+
39+
Primarily when target Git Extensions version change. It gives you the options for possible patches of previous versions.
2840

2941
## Icons
3042

0 commit comments

Comments
 (0)