Skip to content

[Test/do-not-merge] chronus-verify CI smoke test for #46585#46674

Draft
l0lawrence wants to merge 5 commits intomainfrom
test/chronus-verify-ci
Draft

[Test/do-not-merge] chronus-verify CI smoke test for #46585#46674
l0lawrence wants to merge 5 commits intomainfrom
test/chronus-verify-ci

Conversation

@l0lawrence
Copy link
Copy Markdown
Member

Smoke-test PR for the chronus-verify CI workflow added in #46585.

Touches sdk/template/azure-template/ without adding a chronus change entry, so we expect:

  1. Chronus Verify job to fail.
  2. A sticky PR comment to be posted with /chronus add instructions.

The /chronus add slash command itself cannot be tested until #46585 merges (issue_comment workflows only run from the default branch).

Will be closed without merging.

Copilot AI and others added 3 commits April 28, 2026 19:33
On chronus-verify failure, post a sticky PR comment instructing the
contributor to comment '/chronus add [kind]' for a one-click fix.

Add chronus-fix.yml: an issue_comment-triggered workflow that
verifies commenter permissions, rejects fork PRs (security), parses
the requested kind, runs 'chronus add <package> --kind X --message
<PR title>' for each missing package, and pushes the result back to
the PR branch.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions github-actions Bot added the EngSys This issue is impacting the engineering system. label May 1, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 1, 2026

📝 Missing changelog entry

This PR touches package source under sdk/*/*/** but no Chronus
change description was found. CI requires every user-affecting
change to have one.

⚡ One-click fix

Comment /chronus add on this PR and a bot will commit a
changelog entry for you, derived from your PR title.

Customise the entry kind by appending it to the command:

  • /chronus add  →  defaults to internal
  • /chronus add fix  →  bug fix
  • /chronus add feature  →  new feature
  • /chronus add breaking  →  breaking change
  • /chronus add deprecation  →  deprecation
  • /chronus add dependencies  →  dependency bump

ℹ️ For PRs from forks, run the command locally instead:

azpysdk changelog add

See doc/dev/changelog_updates.md for full instructions.

@l0lawrence
Copy link
Copy Markdown
Member Author

/chronus add breaking

Libba Lawrence and others added 2 commits May 1, 2026 14:26
…ghter perms

- Pin actions/checkout, setup-node, github-script to SHA + version comment.
- chronus-fix: restore .github/chronus from base branch before npm ci/run,
  so PR-head changes to the tooling cannot execute under the write token.
- persist-credentials: false on both checkouts; push uses an explicit
  x-access-token URL only at push time.
- Permissions: verify drops pull-requests:write for issues:write only;
  fix drops pull-requests:write to pull-requests:read.
- Slash command parsed by strict regex; rejects /chronus additive etc.
- Add concurrency groups on both workflows.
- Consolidate 4 small github-script steps into one auth+metadata step.
- Merge 4 terminal reply steps into one always() switch step.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Touches sdk/template/azure-template without a chronus changelog entry to
confirm the new chronus-verify workflow posts the sticky one-click-fix
comment. This branch will be closed without merging.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@l0lawrence l0lawrence force-pushed the test/chronus-verify-ci branch from 5184a86 to cb98fb7 Compare May 1, 2026 21:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

EngSys This issue is impacting the engineering system.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants