Skip to content

Conversation

polasudo
Copy link
Contributor

@polasudo polasudo commented Sep 2, 2025

  • Labels: workspace-update, workspace-addition, outside-workspaces, mandatory-workspace
  • Detects required plugins from downstream-plugins file
  • Runs daily at 6 AM UTC

Assisted-by: Cursor

- Labels: workspace-update, workspace-addition, outside-workspaces, mandatory-workspace
- Detects required plugins from downstream-plugins file
- Runs daily at 6 AM UTC

Assisted-by: Cursor
Copy link
Contributor

github-actions bot commented Sep 4, 2025

PR action (/publish) cancelled: PR doesn't touch only 1 workspace.

Copy link
Member

@davidfestal davidfestal left a comment

Choose a reason for hiding this comment

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

The logic that distinguishes between workspace addition and workspace modification might need some rework.

const LABELS = {
UPDATE: 'workspace-update',
ADDITION: 'workspace-addition',
OUTSIDE: 'outside-workspaces',
Copy link
Member

Choose a reason for hiding this comment

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

Not a fan of the 'outside-workspaces' name.


// Check if this is a new workspace
if (file.status === 'added') {
addedWorkspaces.add(workspace);
Copy link
Member

Choose a reason for hiding this comment

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

Is this test sufficient to know that it is the addition of a full workspace that didn't exist before ?
What happens if the PR only add a new file to an already-existing workspace (like a patch file in the /patches sub-folder) ?

Copy link
Member

@davidfestal davidfestal left a comment

Choose a reason for hiding this comment

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

BTW, I think we should also add another label related to the branch the PR is based on.
So we should also do the following changes:

  • Add the mandatory-workspace label only if the PR is based on the main branch
  • Add a release-branch-patch label on workspace PRs based on a release branch

@polasudo polasudo requested a review from davidfestal September 5, 2025 11:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants