Update .github/workflows/generator-generic-ossf-slsa3-publish.yml Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com> Signed-off-by: Huỳnh Thương <252359928+Huynhthuongg@users.noreply.github.com>#33
Conversation
Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com> Signed-off-by: Huỳnh Thương <252359928+Huynhthuongg@users.noreply.github.com>
Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com> Signed-off-by: Huỳnh Thương <252359928+Huynhthuongg@users.noreply.github.com>
Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com> Signed-off-by: Huỳnh Thương <252359928+Huynhthuongg@users.noreply.github.com>
Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com> Signed-off-by: Huỳnh Thương <252359928+Huynhthuongg@users.noreply.github.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 55839d2ae4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback".
| function drawerHTML(){return [['ai','Đoạn chat mới',icons.code],['home','Tìm kiếm đoạn chat',icons.menu],['code','Thư viện',icons.library],['workspace','Dự án',icons.folder],['profile','Ứng dụng',icons.apps]].map(r=>`<button class="drawer-link" data-route="${r[0]}">${r[2]}<span>${r[1]}</span></button>`).join('')} | ||
| function renderChat(){$('#chatLog').innerHTML=entities.messages.map(m=>`<div class="bubble ${m.role==='user'?'user':''}">${esc(m.text)}</div>`).join('')} | ||
| function renderHome(){$('#home').innerHTML=`<div class="hero"><img class="hero-logo" src="1780136894650-Photoroom.png" alt="RKIX3 Logo"><h1>Chúng ta nên bắt đầu từ đâu?</h1><p class="hero-subtitle">Lập trình · Code · Build · Tự động hoá trên một giao diện mobile gọn, sáng và nhanh.</p><div class="prompt-card"><div id="chatLog" class="chat"></div><div class="prompt-row"><button class="prompt-tool" aria-label="Thêm ngữ cảnh">${icons.plus}</button><input id="chatInput" placeholder="Hỏi bất kỳ điều gì"><button class="prompt-tool" aria-label="Ghi âm">${icons.mic}</button><button id="sendChat" class="send-button" aria-label="Gửi">${icons.send}</button></div></div></div><div class="quick-grid">${quick.map(q=>`<button class="quick-card" data-route="${q[0]}">${q[3]}<strong>${q[1]}</strong><span>${q[2]}</span></button>`).join('')}</div>`;renderChat()} | ||
| function renderAI(){$('#ai').innerHTML=`<div class="section-title"><h2>AI thông minh</h2><span class="muted">Online</span></div><div class="panel"><p class="muted">Tập trung cho mobile trước: prompt nhanh, nút mỏng, icon xanh và layout giống app RKIX3 ban đầu.</p><div class="list"><div class="list-item"><span>Generate code</span><span class="status-dot"></span></div><div class="list-item"><span>Debug issue</span><span class="status-dot"></span></div><div class="list-item"><span>Plan sprint</span><span class="status-dot"></span></div></div></div>`} |
There was a problem hiding this comment.
When users open the ai route via the bottom nav or drawer, renderAI() only renders static tool rows and no #chatInput/#sendChat, so the Trợ lý/AI workspace page cannot actually accept prompts. The chat controls were moved into renderHome(), while the new smoke test and README still describe the AI workspace as exposing the chat input/send button, so this route-level regression slips through because the test only checks for those IDs anywhere in the HTML.
Useful? React with 👍 / 👎.
| push: | ||
| branches: | ||
| - '"main"' | ||
| - 'main' |
There was a problem hiding this comment.
Changing this branch filter from the literal "main" branch to main makes the GKE workflow run on every push to the repository's main branch. In the target tree this workflow is still a template: the env block below still uses placeholders such as PROJECT_ID: 'my-project' and a dummy Workload Identity Provider, and there is no Dockerfile for the docker build . step, so enabling the trigger will add a failing CI/deploy run for normal static-site pushes unless the GKE configuration is completed first.
Useful? React with 👍 / 👎.
1 participant
No description provided.