-
Notifications
You must be signed in to change notification settings - Fork 32
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Prepare 4.0.x-devel to become master (#141)
* Refs #20893: Add mirror workflow Signed-off-by: eduponz <[email protected]> * Refs #20893: Add PR template Signed-off-by: eduponz <[email protected]> * Refs #20893: Add more branches to the backport list Signed-off-by: eduponz <[email protected]> --------- Signed-off-by: eduponz <[email protected]>
- Loading branch information
Showing
2 changed files
with
91 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,52 @@ | ||
<!-- Provide a general summary of your changes in the Title above --> | ||
<!-- It must be meaningful and coherent with the changes --> | ||
|
||
<!-- | ||
If this PR is still a Work in Progress [WIP], please open it as DRAFT. | ||
Please consider if any label should be added to this PR. | ||
If no code has been changed, please add `skip-ci` label. | ||
If opening the PR as Draft, please consider adding `no-test` label to only build the code but not run CI. | ||
If documentation PR is still pending, please add `doc-pending` label. | ||
--> | ||
|
||
## Description | ||
|
||
<!-- | ||
Describe changes in detail. | ||
This includes depicting the context, use case or current behavior and describe the proposed changes. | ||
If several features/bug fixes are included with these changes, please consider opening separated pull requests. | ||
--> | ||
|
||
<!-- | ||
In case of bug fixes, please provide the list of supported branches where this fix should be also merged. | ||
Please uncomment following line, adjusting the corresponding target branches for the backport. | ||
--> | ||
<!-- @Mergifyio backport 3.0.x 1.7.x 1.6.x 1.3.x --> | ||
|
||
<!-- If an issue is already opened, please uncomment next line with the corresponding issue number. --> | ||
<!-- Fixes #(issue) --> | ||
|
||
<!-- In case the changes are built over a previous pull request, please uncomment next line. --> | ||
<!-- This PR depends on #(PR) and must be merged after that one. --> | ||
|
||
## Contributor Checklist | ||
|
||
<!-- | ||
- If any of the elements of the following checklist is not applicable, substitute the checkbox [ ] by _N/A_: | ||
- If any of the elements of the following checklist is not fulfilled on purpose, please provide a reason and substitute the checkbox [ ] with ❌: or __NO__:. | ||
--> | ||
|
||
- [ ] Commit messages follow the project guidelines. <!-- External contributors should sign the DCO. Fast DDS developers must also refer to the internal Redmine task. --> | ||
- [ ] Tests that thoroughly check the new feature have been added/Regression tests checking the bug and its fix have been added; the added tests pass locally | ||
- [ ] Any new/modified methods have been properly documented. | ||
- [ ] Changes are backport compatible: they do **NOT** break ABI nor change library core behavior. <!-- Bug fixes should be ABI compatible if possible so a backport to previous affected releases can be made. --> | ||
- [ ] Changes are API compatible. <!-- Public API must not be broken within the same major release. --> | ||
- [ ] Applicable backports have been included in the description. | ||
|
||
## Reviewer Checklist | ||
|
||
- [ ] The PR has a milestone assigned. | ||
- [ ] The title and description correctly express the PR's purpose. | ||
- [ ] Check contributor checklist is correct. | ||
- [ ] Check CI results: changes do not issue any warning. | ||
- [ ] Check CI results: failing tests are unrelated with the changes. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters