-
Notifications
You must be signed in to change notification settings - Fork 178
Add "Docs update" to workflow #746
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
Changes from 4 commits
1476796
79e56f7
4a6c4b5
b88b573
8b03e03
47eb822
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -105,9 +105,9 @@ Refactors are intended for feature releases, if they are not fixing specific iss | |
|
||
Release: feature | ||
|
||
#### New target | ||
#### Target update | ||
|
||
Adding a new target is a change for a patch release because it updates the targets folder implementation. | ||
Updating target implementation (adding a new target or updating already supported target) is a change for a patch release. | ||
|
||
Release: patch | ||
|
||
|
@@ -119,6 +119,18 @@ We consider adding a new functionality to be a feature. It does not matter if it | |
|
||
Release: feature | ||
|
||
#### Docs update | ||
|
||
Documentation changes to markdown files or doxygen documentation (comment-only changes). | ||
|
||
Release: patch | ||
|
||
#### Test update | ||
|
||
Adding a new test unit or test case. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What about updating or removing? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'll change it to "update" There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Fixed, let me know if its OK |
||
|
||
Release: patch | ||
|
||
#### Breaking change | ||
|
||
A breaking change is any change that results in breaking user space. It should have strong justification for us to consider it. Often, such changes can be backward compatible, for example, deprecating the old functionality and introducing the new replacement. | ||
|
@@ -142,10 +154,13 @@ You can see test results [here](just an example). | |
|
||
# Pull request type | ||
|
||
[x] Fix | ||
[ ] Refactor | ||
[ ] New Target | ||
[ ] Feature | ||
[X] Fix | ||
[ ] Refactor | ||
[ ] Target update | ||
[ ] Functionality change | ||
[ ] Docs update | ||
[ ] Test update | ||
[ ] Breaking change | ||
|
||
``` | ||
|
||
|
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.
Updating target implementation -> Updating a target implementation