docs(contest): update name, submission flow (demo repo) and quickapp API#585
Merged
tanghao-xiaomi merged 1 commit intoJun 9, 2026
Conversation
- rename contest to '2026 首届 openvela AI 硬件开发者大赛' across docs - submission deadline 7.1-9.20; align submission flow with the per-team private demo repo plan (direct push, GitHub only, logs auto-collected; winners PR to upstream dev-ai-contest-2026) - hardware-porting track: cross-repo changes go through approval + SCM-provisioned repo (per plan section 2.2) - quickapp_velaclaw: add velaclaw.ask error-code table and Promise usage
tanghao-xiaomi
merged commit 89c7521
into
open-vela:dev-ai-contest-2026
2 of 4 checks passed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note: Please adhere to Contributing Guidelines.
Summary
Update this section with information on why change is necessary,
what it exactly does and how, if new feature shows up, provide
references (dependencies, similar problems and solutions), etc.
Impact
Update this section, where applicable, on how change affects users,
build process, hardware, documentation, security, compatibility, etc.
Testing
Update this section with details on how did you verify the change,
what Host was used for build (OS, CPU, compiler, ..), what Target was
used for verification (arch, board:config, ..), etc. Providing build
and runtime logs from before and after change is highly appreciated.