Skip to content

Update README.md to reflect conductor migration#683

Open
martin-henz wants to merge 2 commits intomasterfrom
martin-henz-patch-1
Open

Update README.md to reflect conductor migration#683
martin-henz wants to merge 2 commits intomasterfrom
martin-henz-patch-1

Conversation

@martin-henz
Copy link
Copy Markdown
Member

adding section on conductor migration

adding section on conductor migration
@martin-henz martin-henz enabled auto-merge (squash) April 24, 2026 03:49
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the README.md file to include a new section regarding the Conductor migration, detailing the associated branch, draft PR, and deployment process. The review feedback suggests improving the documentation's readability and adherence to professional standards by using markdown links for URLs and ensuring proper capitalization of terms like 'Conductor' and 'GitHub Pages'.

Comment thread README.md Outdated
@martin-henz martin-henz changed the title Update README.md Update README.md to reflect conductor migration Apr 24, 2026
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Copy link
Copy Markdown
Member

@RichDom2185 RichDom2185 left a comment

Choose a reason for hiding this comment

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

The workflow for the PR won't run if it's not merged. So there should be no reference to the PR status and just reference the file directly. This should not be a separate PR

@RichDom2185
Copy link
Copy Markdown
Member

The workflow for the PR won't run if it's not merged. So there should be no reference to the PR status and just reference the file directly. This should not be a separate PR

If the other PR is meant to be a development trunk, then the workflow file should be here so it can get merged to main. Otherwise it will never run

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