Skip to content

Commit 43364fb

Browse files
simonbeaudoin0935simonbeaudoin0935
committed
Initial commit
0 parents  commit 43364fb

22 files changed

+1523
-0
lines changed

‎.github/ISSUE_TEMPLATE/bug_report.md‎

Lines changed: 38 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Describe the bug**
11+
A clear and concise description of what the bug is.
12+
13+
**To Reproduce**
14+
Steps to reproduce the behavior:
15+
1. Go to '...'
16+
2. Click on '....'
17+
3. Scroll down to '....'
18+
4. See error
19+
20+
**Expected behavior**
21+
A clear and concise description of what you expected to happen.
22+
23+
**Screenshots**
24+
If applicable, add screenshots to help explain your problem.
25+
26+
**Desktop (please complete the following information):**
27+
- OS: [e.g. iOS]
28+
- Browser [e.g. chrome, safari]
29+
- Version [e.g. 22]
30+
31+
**Smartphone (please complete the following information):**
32+
- Device: [e.g. iPhone6]
33+
- OS: [e.g. iOS8.1]
34+
- Browser [e.g. stock browser, safari]
35+
- Version [e.g. 22]
36+
37+
**Additional context**
38+
Add any other context about the problem here.

‎.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
11+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12+
13+
**Describe the solution you'd like**
14+
A clear and concise description of what you want to happen.
15+
16+
**Describe alternatives you've considered**
17+
A clear and concise description of any alternative solutions or features you've considered.
18+
19+
**Additional context**
20+
Add any other context or screenshots about the feature request here.

‎.github/PULL_REQUEST_TEMPLATE/pr_template.md‎

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
## Pull Request
2+
3+
**Description**
4+
A clear and concise description of what this pull request does.
5+
6+
**Related Issue**
7+
Link to the issue that this pull request addresses (e.g., `Fixes #123`).
8+
9+
**Type of Change**
10+
Please delete options that are not relevant.
11+
- Bug fix (non-breaking change which fixes an issue)
12+
- New feature (non-breaking change which adds functionality)
13+
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
14+
- Documentation update
15+
16+
**Checklist**
17+
- [ ] My code follows the style guidelines of this project
18+
- [ ] I have performed a self-review of my own code
19+
- [ ] I have commented my code, particularly in hard-to-understand areas
20+
- [ ] I have made corresponding changes to the documentation
21+
- [ ] My changes generate no new warnings
22+
- [ ] I have added tests that prove my fix is effective or that my feature works
23+
- [ ] New and existing unit tests pass locally with my changes
24+
- [ ] Any dependent changes have been merged and published in downstream modules
25+
26+
**Additional Context**
27+
Add any other context or screenshots about the pull request here.

‎.github/actions/build_container/action.yml‎

Lines changed: 41 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
name: Builds the container and chroots
2+
description: |
3+
This Github Actions builds the container and sets up the chroot environment for building packages for noble and questing.
4+
5+
inputs:
6+
7+
arch:
8+
description: The architecture to build for. Ex amd64, arm64, etc
9+
required: true
10+
11+
push-to-ghcr:
12+
description: Whether to push the built image to GitHub Container Registry
13+
required: true
14+
default: "true"
15+
16+
token:
17+
description: PAT token
18+
required: true
19+
20+
username:
21+
description: Username for the PAT token
22+
required: true
23+
24+
runs:
25+
using: "composite"
26+
27+
steps:
28+
29+
- name: Build noble and questing containers
30+
shell: bash
31+
run: ./docker_deb_build.py --rebuild
32+
33+
- name: Push to GHCR
34+
if: ${{inputs.push-to-ghcr}} == 'true'
35+
shell: bash
36+
run: |
37+
echo ${{inputs.token}} | docker login ghcr.io -u ${{inputs.username}} --password-stdin
38+
docker push ghcr.io/${{env.QCOM_ORG_NAME}}/${{env.IMAGE_NAME}}:${{inputs.arch}}-noble
39+
docker push ghcr.io/${{env.QCOM_ORG_NAME}}/${{env.IMAGE_NAME}}:${{inputs.arch}}-questing
40+
41+

‎.github/dependabots.yaml‎

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
# To get started with Dependabot version updates, you'll need to specify which
2+
# package ecosystems to update and where the package manifests are located.
3+
# Please see the documentation for all configuration options:
4+
# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
5+
6+
version: 2
7+
updates:
8+
- package-ecosystem: "github-actions" # See documentation for possible values
9+
directory: "/" # This points to .github/workflows
10+
schedule:
11+
interval: "daily"

‎.github/workflows/Readme.md‎

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
# List of workflows and actions
2+
This folder contains workflows that are helpful for maintaining a smooth and secure development process. The workflows should be enabled for open-source projects.
3+
4+
Workflows:
5+
1. `qcom-preflight-checks.yml` - This workflow runs several preflight checks, including copyight, email, repolinter, and security checks. See [qualcomm/qcom-actions](https://github.com/qualcomm/qcom-actions)
6+
2. `stale-issues.yaml` - This workflow will periodically run every 30 days to check for stalled issues and PRs. If the workflow detects any stalled issues and/or PRs, it will automatically leave just a comment to draw attention.

‎.github/workflows/qcom-container-build-and-upload.yml‎

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
name: Container Build And Upload
2+
description: |
3+
Builds and uploads to GHCR (GitHub Container Registry) the container used to build the Qualcomm debian packages.
4+
This workflow will assumes the build architecture is amd64 (x86_64) since the github's 'ubuntu-latest' runs-on tag
5+
is used. Using docker's buildx, the Dockerfile in this repo's docker/ folder will be built for amd64 and cross-compiled
6+
for arm64.
7+
8+
on:
9+
schedule:
10+
# Runs at 00:00 UTC every Monday
11+
- cron: '0 0 * * 1'
12+
13+
pull_request_target:
14+
branches:
15+
- main
16+
paths:
17+
- '.github/workflows/qcom-container-build-and-upload.yml'
18+
- 'docker/**'
19+
20+
push:
21+
branches:
22+
- main
23+
paths:
24+
- '.github/workflows/qcom-container-build-and-upload.yml'
25+
- 'docker/**'
26+
27+
workflow_dispatch:
28+
29+
permissions:
30+
contents: read
31+
32+
env:
33+
QCOM_ORG_NAME: "qualcomm-linux"
34+
35+
IMAGE_NAME: "pkg-builder"
36+
37+
jobs:
38+
39+
# Build the amd64 natively on ubuntu-latest which is an x86_64 host
40+
build-image-amd64:
41+
runs-on: ubuntu-latest
42+
steps:
43+
44+
- name: Checkout Repository
45+
uses: actions/checkout@v4
46+
with:
47+
ref: ${{github.head_ref}}
48+
49+
- name: Build Images
50+
uses: ./.github/actions/build_container
51+
with:
52+
arch: amd64
53+
push-to-ghcr: ${{ github.event_name != 'pull_request_target' }}
54+
token: ${{ secrets.DEB_PKG_BOT_CI_TOKEN }}
55+
username: ${{ vars.DEB_PKG_BOT_CI_USERNAME }}
56+
57+
# Build the arm64 natively using a self-hosted runner on an arm64 host
58+
# Cross compiling the image using buildx on an x86_64 host was tried but failed due to
59+
# issues with qemu and multiarch support in docker buildx.
60+
build-image-arm64:
61+
runs-on: ["self-hosted", "lecore-prd-u2404-arm64-xlrg-od-ephem"]
62+
steps:
63+
64+
- name: Checkout Repository
65+
uses: actions/checkout@v4
66+
with:
67+
ref: ${{github.head_ref}}
68+
69+
- name: Build Images
70+
uses: ./.github/actions/build_container
71+
with:
72+
arch: arm64
73+
push-to-ghcr: ${{ github.event_name != 'pull_request_target' }}
74+
token: ${{ secrets.DEB_PKG_BOT_CI_TOKEN }}
75+
username: ${{ vars.DEB_PKG_BOT_CI_USERNAME }}

‎.github/workflows/qcom-preflight-checks.yml‎

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
name: Qualcomm Preflight Checks
2+
on:
3+
pull_request_target:
4+
branches: [ main ]
5+
push:
6+
branches: [ main ]
7+
workflow_dispatch:
8+
9+
permissions:
10+
contents: read
11+
security-events: write
12+
13+
jobs:
14+
qcom-preflight-checks:
15+
uses: qualcomm/qcom-reusable-workflows/.github/workflows/qcom-preflight-checks-reusable-workflow.yml@v1.1.4
16+
with:
17+
# ✅ Preflight Checkers
18+
repolinter: true # default: true
19+
semgrep: true # default: true
20+
copyright-license-detector: true # default: true
21+
pr-check-emails: true # default: true
22+
dependency-review: true # default: true
23+
secrets:
24+
SEMGREP_APP_TOKEN: ${{ secrets.SEMGREP_APP_TOKEN }}

‎.github/workflows/stale-issues.yaml‎

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
name: 'Close stale issues and pull requests with no recent activity'
2+
on:
3+
schedule:
4+
- cron: "30 1 * * *"
5+
6+
permissions:
7+
issues: write
8+
pull-requests: write
9+
10+
jobs:
11+
stale:
12+
runs-on: ubuntu-latest
13+
steps:
14+
- uses: actions/stale@v9
15+
with:
16+
stale-issue-message: 'This issue has been marked as stale due to 60 days of inactivity. To prevent automatic closure in 10 days, remove the stale label or add a comment. You can reopen a closed issue at any time.'
17+
stale-pr-message: 'This pull request has been marked as stale due to 60 days of inactivity. To prevent automatic closure in 10 days, remove the stale label or add a comment. You can reopen a closed pull request at any time.'
18+
exempt-issue-labels: bug,enhancement
19+
exempt-pr-labels: bug,enhancement
20+
days-before-stale: 60
21+
days-before-close: 10
22+
remove-stale-when-updated: true
23+
remove-issue-stale-when-updated: true
24+
remove-pr-stale-when-updated: true

0 commit comments

Comments
 (0)