| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
Make Arduino CI opt-in via `/run-arduino-tests` comment (#2537) * Make Arduino CI opt-in via /run-arduino-tests comment The Arduino_Compiler_CI workflow has been flaky and only validates a narrow part of the repo (the Arduino compiler), so it no longer runs automatically on every pull request. It now triggers only when a collaborator with write or admin permission comments '/run-arduino-tests' on a PR, or when a maintainer dispatches it manually from the Actions tab. The workflow reacts to the triggering comment with a rocket emoji, posts a 'build started' comment with a link to the run, and posts a final success/failure comment when the build completes. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Document why always() is needed on the report job's if: Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Auto-run Arduino CI on PRs that touch arduino-impacting files Adds a pull_request trigger with a paths filter covering global.json, eng/ArduinoCsCI.cmd, and tools/ArduinoCsCompiler/**. PRs touching any of these still auto-run the check; all other PRs remain opt-in via the /run-arduino-tests comment. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Drop pull-requests: write permission; only issues: write is needed All PR-side writes in this workflow go through the issues API (POST /repos/.../issues/{n}/comments and POST /repos/.../issues/comments/{id}/reactions), both of which only require issues: write. There are no calls to PR-specific endpoints (reviews, requested-reviewers, merge, labels) that would need pull-requests: write. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: joperezr <joperezr@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> | 3 个月前 | |
Migrate to the Locker GitHub action for locking closed/stale issues/PRs (#2182) | 2 年前 | |
Move markdown checks to separate GitHub Actions workflow (#2449) * Initial plan * Make markdown checks optional in Azure pipeline Added a 'runMarkdownChecks' parameter (default: false) to make markdown checks optional. Both markdownlint and markdown-link-check now only run when this parameter is explicitly set to true. This allows users to skip markdown validation checks when they are not needed, while keeping them available for when they are desired. Co-authored-by: krwq <660048+krwq@users.noreply.github.com> * Use boolean parameter directly in conditions Improved conditions to use the boolean parameter directly instead of string comparison, per code review feedback. Co-authored-by: krwq <660048+krwq@users.noreply.github.com> * Make markdown check conditions consistent Moved the PR check condition to job level for Markdown_link_check to be consistent with the markdownlint step. Both now only run on pull requests when the parameter is enabled. Co-authored-by: krwq <660048+krwq@users.noreply.github.com> * Move markdown checks to separate GitHub Actions workflow Moved markdown validation checks from Azure Pipelines to a separate GitHub Actions workflow (similar to Arduino_Compiler_CI). This makes them truly optional - they run on every PR and show failures, but don't block the main Azure pipeline required for merging. Changes: - Created .github/workflows/markdown-checks.yml with markdownlint and markdown-link-check jobs - Removed markdown checks from azure-pipelines.yml - Both checks run on pull_request and workflow_dispatch events - Using continue-on-error to show failures without blocking Co-authored-by: krwq <660048+krwq@users.noreply.github.com> * Remove redundant error suppression in markdown-link-check Removed '|| true' from the markdown-link-check command since the job already uses 'continue-on-error: true' to handle failures properly. Co-authored-by: krwq <660048+krwq@users.noreply.github.com> * Add explicit permissions to markdown checks workflow Added 'permissions: contents: read' to limit GITHUB_TOKEN permissions as recommended by security scan. Co-authored-by: krwq <660048+krwq@users.noreply.github.com> * Remove continue-on-error from markdown checks Removed all continue-on-error directives to match the Arduino workflow pattern. The workflow is optional by default since it's a separate check that can be configured in branch protection settings. Co-authored-by: krwq <660048+krwq@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: krwq <660048+krwq@users.noreply.github.com> | 8 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 3 个月前 | ||
| 2 年前 | ||
| 8 个月前 |