Skip to content

Conversation

@bdougie
Copy link
Collaborator

@bdougie bdougie commented Jul 28, 2025

Description

[ What changed? Feel free to be brief. ]
I have been working on a way to probably track features shipped and properly get them documented in release notes and announcements.

I am introducing a Tier system (WIP) and have created labels for features shipped by the Continue team only (we can expand after we confirm this works).

Thie PR introduces a GitHub Action that labels the merged PR in a tier. This checks the following to determine if a PR needs a label.

  • Is it a Continue team member?
  • Conventional commit includes "feat"
  • Size of the PR

I first created this tier.sh script to confirm it works on the last 100 PRs, and this is to start labeling PRs moving forward. There will still need to be human intervention, but the goal is to do the following.

  1. Start labeling PRs when they are merged
  2. Improve our use of conventional commits in the PR titles.

note: We may want to consider using some other than feat: on PRs that don't need a public announcement

Checklist

  • I've read the contributing guide
  • The relevant docs, if any, have been updated or created
  • The relevant tests, if any, have been updated or created

Screen recording or screenshot

[ When applicable, please include a short screen recording or screenshot - this makes it much easier for us as contributors to review and understand your changes. See this PR as a good example. ]

ysml-edit.mp4

Tests

[ What tests were added or updated to ensure the changes work as expected? ]


Summary by cubic

Added a GitHub Action to automatically label merged PRs by tier based on author, commit type, and PR size.

  • New Features
    • Labels merged PRs from Continue team members as tier 1, 2, or 3 using conventional commit prefixes and change size.
    • Skips labeling for PRs without a relevant commit prefix or from non-team members.

@bdougie bdougie requested a review from a team as a code owner July 28, 2025 19:55
@bdougie bdougie requested review from tingwai and removed request for a team July 28, 2025 19:55
@dosubot dosubot bot added the size:L This PR changes 100-499 lines, ignoring generated files. label Jul 28, 2025
@tingwai tingwai requested review from RomneyDa and removed request for tingwai July 28, 2025 20:39
Copy link
Collaborator

@RomneyDa RomneyDa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will help with better changelogs!

@github-project-automation github-project-automation bot moved this from Todo to In Progress in Issues and PRs Jul 30, 2025
@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Jul 30, 2025
@bdougie bdougie merged commit 7eac665 into main Jul 30, 2025
86 of 88 checks passed
@bdougie bdougie deleted the brian/con-2297-implement-strategy-bdougie-involved-earlier branch July 30, 2025 14:42
@github-project-automation github-project-automation bot moved this from In Progress to Done in Issues and PRs Jul 30, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Jul 30, 2025
@sestinj
Copy link
Contributor

sestinj commented Aug 18, 2025

🎉 This PR is included in version 1.5.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@sestinj
Copy link
Contributor

sestinj commented Aug 18, 2025

🎉 This PR is included in version 1.7.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

lgtm This PR has been approved by a maintainer released size:L This PR changes 100-499 lines, ignoring generated files.

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants