Skip to content

Add select-mode, version, and publish sub-actions#656

Open
bluwy wants to merge 4 commits into
mainfrom
new-version-publish-subaction
Open

Add select-mode, version, and publish sub-actions#656
bluwy wants to merge 4 commits into
mainfrom
new-version-publish-subaction

Conversation

@bluwy

@bluwy bluwy commented Jun 15, 2026

Copy link
Copy Markdown
Member

Adds a very simple implementation of /select-mode, /version, and /publish sub-actions that reuses functions from the root action. I renamed some of the inputs, copied most of the logic over. There's probably more cleanup possible but I don't want to stray too far for now.

I also did not write any readme/docs as I'm lazy maybe it changes after the publish-plan PRs.

I made this PR mainly so we can make updates on it easier later, but I'm also fine closing this as starting from scratch with the publish-plan stuff if that's easier.

@changeset-bot

changeset-bot Bot commented Jun 15, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 9fc1981

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@changesets/action Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Comment thread version/action.yml Outdated
Comment on lines +22 to +23
pr-branch:
description: "Sets the branch in which the action will run. Defaults to `github.ref_name`."

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Unrelated to this PR - but it seems to me this is a somewhat broken/weird input. It only kinda sets the base branch to pr-branch (so maybe this should be called base-branch?) but without actually even checking out this base. So dunno, maybe it kinda works OK for workflows that checkout another base beforehand but we don't make any guarantees here about the outcomes to be particularly coherent.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Ah yeah it should be base-branch. I only read the top of the code and though this was the name of the branch for the PR.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Actually yeah it is kinda weird. Maybe pr-base-branch would be better here? Because we're only using it for the PR's base

Comment thread version/action.yml Outdated
Comment thread src/version/index.ts Outdated
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