Merge ae1e69d into 5983a65

Author: OS-katherinebatista

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @OutSystems/data-fabric-clients

.github/ISSUE_TEMPLATE/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,22 @@
+<!-- 
+You can check for more info about PR conventions here https://outsystemsrd.atlassian.net/wiki/spaces/RCP/pages/1544487638/Pull+Requests
+Conventions: <jira-issue>: <subject>
+<jira-issue> -  Issue id, eg: RSAT-0000 (no need for # as in svn). This will link the branch and later on the pull request to the issue id in Jira
+<subject> - a short and concise description of the changes, usually the summary of the jira issue
+ -->
+
+### Jira Issue
+<!-- Please change the <jira-issue> tag to your jira issue (ex: RAR-131) -->
+
+[<jira-issue>](https://outsystemsrd.atlassian.net/browse/<jira-issue>)
+
+### Context
+<!--- Why is this change required? What problem does it solve? -->
+
+### Impacts
+<!-- What are the consequences of the changes and possible implications in clients -->
+- [ ] Breaking Change
+    - [ ] Behavioral breaking change
+    - [ ] Breaks existent APIs  
+- [ ] Refactor (big refactor on a sensitive asset )
+- [ ] Requires revision on public documentation

.github/ISSUE_TEMPLATE/bug.yaml

@@ -0,0 +1,11 @@
+name: Validate pull request labels
+
+
+on:
+  pull_request:
+    types: [labeled, unlabeled, synchronize]
+
+
+jobs:
+  check-label:
+    uses: OutSystems/rd.github-reusable-workflows/.github/workflows/validate-pr-labels.yaml@v1.0.0

.github/ISSUE_TEMPLATE/config.yaml

@@ -0,0 +1,11 @@
+name: Validate pull request title
+
+
+on:
+  pull_request:
+    types: [opened, edited, synchronize, reopened]
+
+
+jobs:
+  build:
+    uses: OutSystems/rd.github-reusable-workflows/.github/workflows/validate-pr-title.yaml@v1.0.0