Conversation
- Initialize package.json with dependencies and scripts for the Webflow OAuth tool. - Implement main functionality in src/index.ts to handle OAuth flow, including authorization, token exchange, and server setup. - Configure TypeScript settings in tsconfig.json for the project.
…and provider configuration - Implemented Provider resource for Webflow API authentication. - Added Redirect resource to manage HTTP redirects for Webflow sites. - Created RobotsTxt resource for configuring robots.txt file for Webflow sites. - Developed Site resource for programmatically managing Webflow sites, including properties like display name, custom domains, and publishing options. - Introduced pulumi-plugin.json for plugin metadata.
… and Site - Created `pulumi-plugin.json` for Webflow resource management. - Added `Redirect` resource with properties for managing HTTP redirects. - Implemented `RobotsTxt` resource for configuring robots.txt content. - Developed `Site` resource for managing Webflow sites, including display name, workspace ID, and optional settings. - Included type hints and documentation for all resource properties and methods.
…ation - Fixed package.json configuration: updated package name to @pulumi/webflow and added necessary npm publishing fields (description, keywords, license, author). - Enhanced TypeScript configuration for distribution, ensuring declaration files are generated and types are correctly referenced. - Added support for both ESM and CJS module systems in package.json. - Created GitHub Actions workflow for automated npm publishing on release tags, including dry-run and provenance support. - Developed comprehensive TypeScript SDK documentation, including installation instructions, code examples, and troubleshooting guidance. - Validated npm package installation and end-to-end functionality of the TypeScript SDK.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR introduces initial provider features by adding comprehensive workflows for creating modules, agents, and workflows within the BMAD system. The changes establish a structured, step-based approach for building BMAD components with detailed guidance and validation.
Key Changes:
- Added complete create-module workflow with 11 sequential steps for module construction
- Added create-agent workflow with 11 steps for agent development
- Added create-workflow workflow with 8 steps for workflow design and generation
- Included supporting templates, validation checklists, and reference examples
Reviewed changes
Copilot reviewed 138 out of 584 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| create-workflow steps (01-08) | Step-by-step workflow creation process from initialization through validation |
| create-module workflow + steps | Complete module creation system with agent, workflow, and installer setup |
| create-agent workflow + steps | Agent building process from brainstorming through celebration |
| Templates and validation files | Supporting structures for module.yaml, agents, workflows, and validation |
| Reference examples | Sample meal-prep workflow and agent examples for guidance |
Comments suppressed due to low confidence (1)
.bmad/bmb/workflows/create-module/steps/step-11-validate.md:336
- There's an extra closing code fence (```) at the end of the file that doesn't have a corresponding opening fence. This should be removed.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - IF A: Execute {advancedElicitationTask} | ||
| - IF P: Execute {partyModeWorkflow} | ||
| - IF C: Append requirements to {workflowPlanFile}, update frontmatter, then load, read entire file, then execute {nextStepFile} | ||
| - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#8-present-menu-options) |
There was a problem hiding this comment.
| When user selects [C], provide these instructions: | ||
|
|
||
| **🎯 Workflow Creation Complete! Your new workflow is ready at:** | ||
| `{target_workflow_path}` |
There was a problem hiding this comment.
Variable name inconsistency: uses {target_workflow_path} here but the frontmatter defines it as targetWorkflowPath (camelCase). Should be {targetWorkflowPath} for consistency.
JDetmar
added a commit
that referenced
this pull request
Jan 12, 2026
… update Webflow API does not support PATCH for registered scripts, which caused 404 errors when Pulumi tried to update them. This change: - Changes all property diffs to use UpdateReplace instead of Update - Makes version field required (removes optional workaround) - Updates Update method to return error as safety net - Adds deprecation comment to PatchRegisteredScript function - Adds tests for replacement behavior and Update error Fixes issues #1 and #4 from ISSUES-TO-FIX.md. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
4 tasks
JDetmar
added a commit
that referenced
this pull request
Jan 12, 2026
… update Webflow API does not support PATCH for registered scripts, which caused 404 errors when Pulumi tried to update them. This change: - Changes all property diffs to use UpdateReplace instead of Update - Makes version field required (removes optional workaround) - Updates Update method to return error as safety net - Adds deprecation comment to PatchRegisteredScript function - Adds tests for replacement behavior and Update error Fixes issues #1 and #4 from ISSUES-TO-FIX.md. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
JDetmar
added a commit
that referenced
this pull request
Jan 12, 2026
… update (#51) Webflow API does not support PATCH for registered scripts, which caused 404 errors when Pulumi tried to update them. This change: - Changes all property diffs to use UpdateReplace instead of Update - Makes version field required (removes optional workaround) - Updates Update method to return error as safety net - Adds deprecation comment to PatchRegisteredScript function - Adds tests for replacement behavior and Update error Fixes issues #1 and #4 from ISSUES-TO-FIX.md. Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.