Add monthly cron workflow for label updates

[snovak7]

Closes #26

Summary by CodeRabbit

• Chores
  • Introduced a scheduled workflow to automatically update issue labels monthly.

[coderabbitai]

Walkthrough

A new GitHub Actions workflow, "Monthly Label Timer," has been added. This workflow runs monthly and on manual trigger, prevents overlapping runs, and calls a reusable label update workflow from the escendit/keystone repository, inheriting repository secrets and setting appropriate permissions for label management.

Changes

Cohort / File(s)	Change Summary
New Scheduled Label Sync Workflow .github/workflows/cron-update-labels.yml	Added a workflow to trigger monthly or manually, uses concurrency control, and calls an external reusable workflow for label management.

Sequence Diagram(s)

sequenceDiagram
    participant GitHub Scheduler
    participant Monthly Label Timer Workflow
    participant escendit/keystone Utility Workflow

    GitHub Scheduler->>Monthly Label Timer Workflow: Trigger (cron or manual)
    Monthly Label Timer Workflow->>Monthly Label Timer Workflow: Enforce concurrency, set permissions
    Monthly Label Timer Workflow->>escendit/keystone Utility Workflow: Invoke reusable workflow with secrets
    escendit/keystone Utility Workflow-->>Monthly Label Timer Workflow: Update labels

Loading

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Assessment against linked issues

Objective	Addressed	Explanation
Sync Labels from a Reusable Workflow from a Keystone repository (#26)	✅

Poem

Each month at dawn, the labels align,
A timer ticks in workflow design.
From Keystone’s vault, the labels flow,
With secrets safe, the issues grow.
A rabbit hops with glee and pride—
Automation’s magic, on this ride!
🐇✨

Note

🔌 MCP (Model Context Protocol) integration is now available in Early Access!

Pro users can now connect to remote MCP servers under the Integrations page to get reviews and chat conversations that understand additional development context.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 26-sync-labels-from-a-reusable-workflow-from-a-keystone-repository

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

.github/workflows/cron-update-labels.yml (1)

11-15: Concurrency LGTM; consider a more generic group key.

Using github.workflow improves future-proofing if the workflow name changes or is reused.

Apply this minimal change:

-  group: labels-monthly-${{ github.ref }}
+  group: ${{ github.workflow }}-${{ github.ref }}

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8c358da and f4064cc.

📒 Files selected for processing (1)

• .github/workflows/cron-update-labels.yml (1 hunks)

🔇 Additional comments (4)

.github/workflows/cron-update-labels.yml (4)

1-2: Meets the objective (monthly label sync via reusable workflow).

Title and purpose are clear and aligned with issue #26.

---

7-9: Validate the cron timing and timezone.

Cron runs at 01:29 UTC on the 1st of each month. Confirm this matches your intended local time and cadence.

---

16-20: Permissions look minimal; confirm they match the called workflow’s needs.

issues: write should be sufficient for label management. Verify the reusable workflow doesn’t require contents: write or additional scopes (e.g., pull-requests: write).

---

23-26: ✔ Reusable workflow call verified

• The file escendit/keystone/.github/workflows/utility-update-labels.yml exists on main.
• It declares on: workflow_call, making it callable.
• It defines permissions: issues: write, which covers all label-creation/update operations.
• Passing secrets: inherit will supply the required GITHUB_TOKEN.

No further changes needed.