Update action.yml for features

[luke-truitt]

Summary by CodeRabbit

• Refactor
  • Modified build process inputs: Removed pid and pid_env_var inputs and introduced a new feature input for specifying build features.

[coderabbitai]

Walkthrough

The recent update streamlines the build process by focusing on feature-specific builds. It removes the previously required pid and pid_env_var inputs, simplifying configuration. Instead, a new feature input has been introduced, allowing users to specify which feature to build. The build command has been adapted to utilize the --features flag, directly linking the specified feature for a more targeted build approach.

Changes

File(s)	Change Summary
action.yml	Removed pid, pid_env_var inputs; added feature input

🐇✨
In the realm of code, where changes abide,
A rabbit hopped through, with a joyful stride.
"Away with the old, in with the new," it cheered,
As pid and pid_env_var disappeared.
Now feature shines, a beacon so bright,
Guiding the builds through the night.
🌟🐾

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

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>.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @coderabbitai modularize this function.
• 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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/coderabbit-overrides.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

Review Status

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 3d37275 and d396408.

Files selected for processing (1)

• action.yml (2 hunks)

Additional comments not posted (1)

action.yml (1)

8-9: The addition of the feature input is correctly implemented and aligns with the PR objectives.

[coderabbitai]

Enclose the feature input variable in quotes to prevent issues with feature names containing spaces or special characters.

-        anchor build --features=${{ inputs.feature }}
+        anchor build --features="${{ inputs.feature }}"

---

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change

	anchor build --features=${{ inputs.feature }}
	anchor build --features="${{ inputs.feature }}"