Skip to content

Add radxa-dragon-q6a to nightly release blacklist#260

Merged
igorpecovnik merged 2 commits into
mainfrom
q6a
Mar 25, 2026
Merged

Add radxa-dragon-q6a to nightly release blacklist#260
igorpecovnik merged 2 commits into
mainfrom
q6a

Conversation

@igorpecovnik
Copy link
Copy Markdown
Member

@igorpecovnik igorpecovnik commented Mar 25, 2026

Summary

  • Adds radxa-dragon-q6a to the nightly release blacklist

@HeyMeco revert once aic driver is in shape.

Test plan

  • Verify the board is correctly excluded from nightly release builds

@github-actions github-actions Bot added 05 Milestone: Second quarter release size/small PR with less then 50 lines Needs review Seeking for review labels Mar 25, 2026
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Mar 25, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 3f2ad335-421f-4f1b-a20c-6c66e10c683b

📥 Commits

Reviewing files that changed from the base of the PR and between a35c357 and 710b8a3.

📒 Files selected for processing (1)
  • release-targets/targets-release-nightly.blacklist
✅ Files skipped from review due to trivial changes (1)
  • release-targets/targets-release-nightly.blacklist

Walkthrough

Two target identifiers, radxa-dragon-q6a and dg-svr-865-tiny, were added to the nightly release blacklist file release-targets/targets-release-nightly.blacklist, excluding these targets from automated nightly releases.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Title check ⚠️ Warning The title mentions adding radxa-dragon-q6a to the nightly release blacklist, but the changeset adds two targets: radxa-dragon-q6a and dg-svr-865-tiny. The title only references one of the two changes. Update the title to reflect both targets being added, such as 'Add radxa-dragon-q6a and dg-svr-865-tiny to nightly release blacklist' or clarify which target is the main focus.
✅ Passed checks (2 passed)
Check name Status Explanation
Description check ✅ Passed The description addresses the main purpose of the changeset by noting the addition to the nightly release blacklist and mentions reverting once driver issues are resolved.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch q6a

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
release-targets/targets-release-nightly.blacklist (1)

1-25: Consider alphabetically sorting the blacklist for easier maintenance.

While the new entry is correct, the file would benefit from consistent alphabetical ordering. Currently, entries like oneplus-kebab, xiaomi-elish, uefi-x86, and the mekotronics boards are out of alphabetical sequence. If alphabetically sorted, radxa-dragon-q6a would appear between radxa-zero (line 16) and renegade (line 17).

This is purely a maintainability consideration and doesn't affect functionality.

📋 Proposed alphabetically sorted version
 bananapim2pro
 bananapi-m2s
 jethub-d1
 jethub-h1
 jethubj80
 jethubj100
 jethubj200
 khadas-vim1
 khadas-vim2
 lafrite
 lepotato
+mekotronics-r58-4x4
+mekotronics-r58hd
 odroidc2
 olimex-teres-a64
 onecloud
+oneplus-kebab
 pine64
+radxa-dragon-q6a
 radxa-zero
 renegade
 tritium-h3
 tritium-h5
-oneplus-kebab
-xiaomi-elish
 uefi-x86
-mekotronics-r58-4x4
-mekotronics-r58hd
-radxa-dragon-q6a
+xiaomi-elish
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@release-targets/targets-release-nightly.blacklist` around lines 1 - 25, The
blacklist entries should be alphabetized for maintainability: reorder the lines
so entries are in ascending alphabetical order (e.g., place radxa-dragon-q6a
between radxa-zero and renegade) and move mekotronics-r58-4x4 /
mekotronics-r58hd, oneplus-kebab, uefi-x86, and xiaomi-elish into their correct
alphabetic positions; update the file so every line is sorted lexicographically
while preserving the same entries.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@release-targets/targets-release-nightly.blacklist`:
- Around line 1-25: The blacklist entries should be alphabetized for
maintainability: reorder the lines so entries are in ascending alphabetical
order (e.g., place radxa-dragon-q6a between radxa-zero and renegade) and move
mekotronics-r58-4x4 / mekotronics-r58hd, oneplus-kebab, uefi-x86, and
xiaomi-elish into their correct alphabetic positions; update the file so every
line is sorted lexicographically while preserving the same entries.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9d9cfbb5-bee5-4a16-8fc0-8b69a6afbb57

📥 Commits

Reviewing files that changed from the base of the PR and between 635354f and a35c357.

📒 Files selected for processing (1)
  • release-targets/targets-release-nightly.blacklist

@igorpecovnik igorpecovnik merged commit d3b71a3 into main Mar 25, 2026
7 checks passed
@igorpecovnik igorpecovnik deleted the q6a branch March 25, 2026 14:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

05 Milestone: Second quarter release Needs review Seeking for review size/small PR with less then 50 lines

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant