1b:I[40533,["7374","static/chunks/7374-3d45d9728b4c7a58.js","3612","static/chunks/3612-66a9492c59acfe17.js","6585","static/chunks/6585-c1bc043b2493ff06.js","909","static/chunks/909-63c127a841bfbdd9.js","9665","static/chunks/9665-b274c6a6f1fd7aae.js","6269","static/chunks/6269-e671b9ace1d878c3.js","9411","static/chunks/app/%5Blocale%5D/(default)/categories/page-ab399fb789661555.js"],"default"] 1c:T6f3,

GitHub Actions for Plane-MCP

This folder contains the GitHub Actions workflows configured for this project.

Secret Configuration

For integration tests to work correctly on GitHub Actions, you need to configure the following secrets in your GitHub repository settings:

TEST_PLANE_TOKEN_API: Your Plane.so API key for testing
TEST_PLANE_WORKSPACE_SLUG: Your Plane.so workspace slug (e.g., "your-organization")

How to Configure Secrets

Go to your GitHub repository
Navigate to "Settings" > "Secrets and variables" > "Actions"
Click on "New repository secret"
Add the two secrets mentioned above

Available Workflows

test-endpoints.yml

This workflow tests the Plane API endpoints. It is triggered in the following cases:

When pushing to main/master branches
When creating a pull request to main/master
Manually via the GitHub Actions interface
Automatically every day at midnight (00:00 UTC)

It runs two jobs:

unit-tests: Runs all unit tests
integration-tests: Runs integration tests and the endpoint verification script

Manual Execution

To manually run tests via GitHub Actions:

Go to the "Actions" tab of your repository
Select the "Test API Endpoints" workflow in the sidebar
Click

Categories

Current Category: biomejs

plane-mcp-server