⚠ This page is served via a proxy. Original site: https://github.com
This service does not collect credentials or authentication data.
Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Jan 15, 2026

  • Clone modules from envoyproxy/bazel-registry repository
  • Create bazel-registry directory structure in toolshed
  • Copy modules directory to toolshed/bazel-registry/modules
  • Update .gitignore to allow bazel-registry directory
  • Create .github/workflows/bazel-registry.yml with boilerplate
  • Add request job to check if workflow should run
  • Add final status job "Bazel registry CI"
  • Add validation job to check module structure
  • Refactor to use actions/jq and actions/bson per repo style
  • Use actions/jq for JSON validation instead of inline jq
  • Use actions/bson for bash scripting
  • Add BCR presubmit test job with Bazelisk
  • Test the workflow configuration
  • Address code review feedback
  • (Stretch goal) BCR-style validation infrastructure
Original prompt

i just added a new repo envoyproxy/bazel-registry - this was a wrong turn - i should have added this to toolshed which is already well setup for monorepo testing

so basically the task is this - genesis of toolshed/bazel-registry

copy the modules folder from bazel-registry -> toolshed/bazel-registry/modules (ie toolshed/bazel-registry will be the registry root)

we will get some linting out of the box - but we need to do someting like what the other ci aspects do - ie add .github/workflows/bazel-registry.yml

it needs the boilerplate - request and final status "Bazel registry CI" job

stretch goal is to add some actual bcr-style testing so we can catch issues before upstreaming our fixes


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

@netlify
Copy link

netlify bot commented Jan 15, 2026

Deploy Preview for nifty-bassi-e26446 ready!

Name Link
🔨 Latest commit 2ba61dc
🔍 Latest deploy log https://app.netlify.com/projects/nifty-bassi-e26446/deploys/6969fbc260379b0008f9b676
😎 Deploy Preview https://deploy-preview-3487--nifty-bassi-e26446.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copilot AI changed the title [WIP] Add bazel-registry to toolshed with CI setup Migrate bazel-registry from standalone repo to toolshed monorepo Jan 15, 2026
Copilot AI requested a review from phlax January 15, 2026 23:19
@phlax
Copy link
Member

phlax commented Jan 15, 2026

cc @jwendell - thankyou!!!

@phlax
Copy link
Member

phlax commented Jan 15, 2026

@copilot good job so far - the ci needswork

we have a style - and it revolves around the jq action defined in actions/jq - se allso actions/bson for bashing - this is not that style

you can use path to actions/etc directly for this pr

Copy link
Contributor Author

Copilot AI commented Jan 15, 2026

@copilot good job so far - the ci needswork

we have a style - and it revolves around the jq action defined in actions/jq - se allso actions/bson for bashing - this is not that style...

Refactored the CI to use the actions/jq and actions/bson style in commit 1ee4510. The validation now uses:

  • actions/bson for bash scripting to check module structure
  • actions/jq to validate all JSON files (metadata.json and source.json)
  • Relative paths (./actions/jq, ./actions/bson) as requested

@phlax phlax force-pushed the copilot/add-bazel-registry-to-toolshed branch 4 times, most recently from ee2f1bf to d5dd8c2 Compare January 16, 2026 08:35
@phlax phlax force-pushed the copilot/add-bazel-registry-to-toolshed branch from b9ae09d to d153722 Compare January 16, 2026 08:43
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