update .github

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -0,0 +1,45 @@
+name: Bug report
+description: Create a report to help us improve
+title: Bug report
+labels: ["bug :bug:"]
+body:
+  - type: textarea
+    id: bug_report_description
+    attributes:
+      label: Describe the bug
+      description: A clear and concise description of what the bug is
+    validations:
+      required: true
+  - type: textarea
+    id: bug_report_reproduce
+    attributes:
+      label: To reproduce
+      description: Steps to reproduce the behavior
+    validations:
+      required: true
+  - type: textarea
+    id: bug_report_expected_behavior
+    attributes:
+      label: Expected behavior
+      description: A clear and concise description of what you expected to happen
+    validations:
+      required: true
+  - type: textarea
+    id: bug_report_screenshots
+    attributes:
+      label: Screenshots
+      description: |
+        If applicable, add screenshots to help explain your problem
+        Tip: You can attach images by clicking this area to highlight it and then dragging files in.
+  - type: textarea
+    id: bug_report_desktop
+    attributes:
+      label: OS (please complete the following information)
+      placeholder: |
+        - OS: [e.g. Ubuntu]
+        - Version: [e.g. 22.04]
+  - type: textarea
+    id: bug_report_additional_context
+    attributes:
+      label: Additional context
+      description: Add any other context about the problem here

.github/ISSUE_TEMPLATE/feature_request.yaml

@@ -0,0 +1,29 @@
+name: Feature request
+description: Suggest an idea for this project
+title: Feature request
+labels: ["feature :sparkles:"]
+body:
+  - type: textarea
+    id: feature_request_description
+    attributes:
+      label: Is your feature request related to a problem? Please describe.
+      description: A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+    validations:
+      required: true
+  - type: textarea
+    id: feature_request_solution_description
+    attributes:
+      label: Describe the solution you'd like
+      description: A clear and concise description of what you want to happen
+    validations:
+      required: true
+  - type: textarea
+    id: feature_request_alternatives
+    attributes:
+      label: Describe alternatives you've considered
+      description: A clear and concise description of any alternative solutions or features you've considered
+  - type: textarea
+    id: feature_request_additional_context
+    attributes:
+      label: Additional context
+      description: Add any other context or screenshots about the feature request here

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md

@@ -0,0 +1,35 @@
+## Description
+
+Please include a summary of the changes and the related issue. Please also include relevant motivation and context.
+
+## Type of change
+
+Please delete options that are not relevant.
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] This change requires a documentation update
+
+## How Has This Been Tested?
+
+Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.
+
+- [ ] Test A
+- [ ] Test B
+
+**Test Configuration**:
+* OS version:
+* Hardware:
+* SDK:
+
+## Checklist:
+
+- [ ] My code follows the style guidelines of this project
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally with my changes
+- [ ] Any dependent changes have been merged and published in downstream modules

.github/workflows/build-check-sdk.yaml

@@ -0,0 +1,68 @@
+name: Build Test with SDK
+
+on: [push, pull_request]
+
+env:
+  PERSIST_DIR: /srv/gh-runners/quic-qrb-ros
+  DL_DIR: /srv/gh-runners/quic-qrb-ros/downloads
+  WORKSPACE: ${{ github.workspace }}/ros_ws
+  SDK_DIR: ${{ github.workspace }}/sdk
+
+jobs:
+  build:
+    runs-on: [self-hosted, x86]
+    timeout-minutes: 720
+    steps:
+      - name: Set up SDK
+        run: |
+          set -x
+          if [ -e ${PERSIST_DIR} ] && [ -r ${PERSIST_DIR} ] && [ -x ${PERSIST_DIR} ];then
+            echo "Setting up SDK..."  
+            umask 022
+            ${PERSIST_DIR}/sdk/qcom-robotics-ros2-humble-x86_64-qcom-robotics-full-image-armv8-2a-qcs6490-rb3gen2-vision-kit-toolchain-1.0.sh <<EOF
+            ${SDK_DIR}
+            Y
+          EOF
+          else
+            echo "Downloading SDK from CLO..."
+            wget -q https://artifacts.codelinaro.org/artifactory/qli-ci/flashable-binaries/qirpsdk/qcs6490-rb3gen2-vision-kit/x86/qcom-6.6.38-QLI.1.2-Ver.1.1_robotics-product-sdk-1.1.zip
+            if [ $? != 0 ];then
+              Download SDK failed!!!. Exit!.
+              exit 2
+            fi
+            unzip qcom-6.6.38-QLI.1.2-Ver.1.1_robotics-product-sdk-1.1.zip
+            echo "Setting up SDK..."
+
+            umask 022
+            ./target/qcs6490-rb3gen2-vision-kit/sdk/qcom-robotics-ros2-humble-x86_64-qcom-robotics-full-image-armv8-2a-qcs6490-rb3gen2-vision-kit-toolchain-1.0.sh <<EOF
+            ${SDK_DIR}
+            Y
+          EOF
+          fi
+
+      - name: Checkout repo
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          path: ${{ github.workspace }}/ros_ws/${{ github.event.repository.name }}
+
+      - name: Download dependencies
+        run: |
+          cd ${WORKSPACE}
+          # no QRB ROS dependencies
+        
+      - name: build
+        run: |
+          cd ${SDK_DIR}
+          umask 022
+          . environment-setup-armv8-2a-qcom-linux
+          cd ${WORKSPACE}
+          export AMENT_PREFIX_PATH="${OECORE_TARGET_SYSROOT}/usr;${OECORE_NATIVE_SYSROOT}/usr"
+          export PYTHONPATH=${PYTHONPATH}:${OECORE_TARGET_SYSROOT}/usr/lib/python3.10/site-packages
+
+          colcon build --merge-install --cmake-args \
+            -DPython3_ROOT_DIR=${OECORE_TARGET_SYSROOT}/usr \
+            -DPython3_NumPy_INCLUDE_DIR=${OECORE_TARGET_SYSROOT}/usr/lib/python3.10/site-packages/numpy/core/include \
+            -DPYTHON_SOABI=cpython-310-aarch64-linux-gnu -DCMAKE_STAGING_PREFIX=$(pwd)/install \
+            -DCMAKE_PREFIX_PATH=$(pwd)/install/share \
+            -DBUILD_TESTING=OFF

.github/workflows/cpp-code-style-checker.yml

@@ -0,0 +1,36 @@
+name: Cpp Code Style Checker
+
+on: [push, pull_request, workflow_dispatch]
+
+jobs:
+  cpp-code-style-check:
+    runs-on: ubuntu-latest
+
+    steps:
+    - name: Checkout code
+      uses: actions/checkout@v4
+
+    - name: Install clang-format
+      run: sudo apt install -y clang-format
+
+    - name: Setup clang-format configuration
+      run: |
+        if [ ! -f ./.clang-format ]; then
+          echo "No .clang-format found, will use default configuration"
+          curl -o .clang-format https://raw.githubusercontent.com/quic-qrb-ros/.github/main/code-style-profiles/.clang-format
+        fi
+
+    - name: Check code style
+      run: |
+        SRC=$(git ls-tree --full-tree -r HEAD | grep -e "\.\(c\|h\|hpp\|cpp\)\$" | cut -f 2)
+
+        echo -e "Check source files: \n$SRC\n"
+        clang-format -style=file -i $SRC
+
+        if ! git diff --exit-code; then
+          echo -e "\nCode does not match required style !!!"
+          echo "Please use clang-format to format your code."
+          exit 1
+        else
+          echo "All files are properly formatted."
+        fi

.github/workflows/quic-organization-repolinter.properties.json

@@ -0,0 +1,5 @@
+{
+    "name": "QuIC Organization Repolinter Workflow",
+    "description": "QuIC Organization Repolinter workflow template.",
+    "iconName": "todo"
+}