issues Search Results · language:Dune language:JavaScript language:JavaScript language:JavaScript language:CSS
Filter by
20.6M results
Part of the release-hardening epic (repo-hygiene, release). Do last — captures the decisions from (A)–(F).
Problem
The release process currently lives scattered across AGENTS.md sections, the Copilot ...
documentation
release
repo-hygiene
Part of the release-hardening epic (repo-hygiene, release). Depends on (A), (B), (C). Process only — this does not cover
the v2 feature coding (e.g. RegExp machine support).
Goal
Walk a hypothetical ...
github_actions
release
repo-hygiene
Part of the release-hardening epic (repo-hygiene, release).
Problem
When the owner leaves code-review comments on a PR whose branch is governed by rulesets (PR required, no direct push),
the agent has ...
documentation
release
repo-hygiene
Part of the release-hardening epic (repo-hygiene, release).
Problem
Copilot / bot-authored PRs (e.g. v1.7 #260) get all workflow runs stuck in action_required (0s) until a maintainer
clicks Approve and ...
github_actions
release
repo-hygiene
Part of the release-hardening epic (repo-hygiene, release).
Problem
Re-pointing an existing vX.Y.Z tag (done during v1.7 troubleshooting) requires temporarily adding a RepositoryRole
bypass to the v* ...
github_actions
release
repo-hygiene
Part of the release-hardening epic (repo-hygiene, release).
Problem
Release PRs that touch protected files (the PROTECTED_FILES.json set) trip the fail-closed, no-bypass lock-files gate
(scripts/check-protected-files.mjs). ...
github_actions
release
repo-hygiene
There is a mismatch between the settings block 5. Dots and corner shapes for error correction and the actually produced
QR code if it includes a logo. Regardless of what is chosen the error correction ...
Part of the release-hardening epic (repo-hygiene, release).
Problem
The integration → master release PR can t be merged without temporarily setting the main ruleset s
required_approving_review_count ...
github_actions
release
repo-hygiene
Add a CI pipeline that runs lint and tests automatically on every push and pull request to main, for both backend and
frontend.
chore
计划加入一个编译开发镜像(后端保持当前现状,但是前端改为不需要编译,直接npm run dev,并且提供出一个/app目录,从而可以直接方便从容器外部映射前端app目录进来
plan

Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip! Restrict your search to the title by using the in:title qualifier.