Skip to content

prjtrellis@0.0.0-20251212-e076bca#6801

Closed
MrAMS wants to merge 1 commit into
bazelbuild:mainfrom
MrAMS:prjtrellis-v0.0.0-20251212-e076bca
Closed

prjtrellis@0.0.0-20251212-e076bca#6801
MrAMS wants to merge 1 commit into
bazelbuild:mainfrom
MrAMS:prjtrellis-v0.0.0-20251212-e076bca

Conversation

@MrAMS

@MrAMS MrAMS commented Dec 12, 2025

Copy link
Copy Markdown
Contributor

@bazel-io

Copy link
Copy Markdown
Member

Hello @UebelAndre, modules you maintain (prjtrellis) have been updated in this PR.
Please review the changes. You can view a diff against the previous version in the "Generate module diff" check.

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

Copy link
Copy Markdown
Contributor

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 adds the version 0.0.0-20251212-e076bca for the prjtrellis module. While the new version's files (MODULE.bazel, presubmit.yml, etc.) appear to be correctly structured, this PR introduces a critical issue by modifying modules/prjtrellis/metadata.json. It changes the module's homepage, maintainer, and source repository to point to a fork. This is a significant change that effectively transfers ownership of the module and violates the Bazel Central Registry's 'add-only' policy for non-versioned files. Such a change requires manual review and approval from BCR maintainers. If the intention is to publish a fork as a separate module, it should be given a distinct name.

Comment on lines +2 to 13
"homepage": "https://github.com/MrAMS/prjtrellis",
"maintainers": [
{
"email": "26427366+UebelAndre@users.noreply.github.com",
"github": "UebelAndre",
"github_user_id": 26427366,
"name": "UebelAndre"
"email": "",
"github": "MrAMS",
"name": "Qijia Yang",
"github_user_id": 25056812
}
],
"repository": [
"github:YosysHQ/prjtrellis"
"github:MrAMS/prjtrellis"
],

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

critical

This pull request modifies the homepage, maintainers, and repository fields for the existing prjtrellis module, effectively transferring ownership from the original YosysHQ/prjtrellis to the MrAMS/prjtrellis fork. This is a significant and potentially breaking change for existing users of this module.

This change violates two key BCR policies:

  1. Add-only rule (line 13): Pull requests should be 'add-only' and not mutate non-module files when adding a new version. Modifying metadata.json to change ownership affects all versions of the module.
  2. Significant changes review (line 62): The style guide requires a manual review by @bazelbuild/bcr-maintainers for any significant changes to the maintainers or repository fields. This change from an organization repo to a personal fork is a very significant change.

If this is a fork that should coexist with the original, it should be published under a new module name (e.g., mrams-prjtrellis). If this is an intentional transfer of ownership, it requires explicit approval from the original maintainers and the BCR team.

References
  1. Per line 13 of the style guide: PRs should be 'add-only' and not mutate non-module files (like metadata.json) when adding a new version. This PR modifies the homepage, maintainers, and repository fields, which affects the entire module. (link)
  2. Per line 62 of the style guide: Significant changes to maintainers or repository fields in metadata.json require a manual review by BCR maintainers. This change from YosysHQ/prjtrellis to a fork is a significant change. (link)

@MrAMS

MrAMS commented Dec 12, 2025

Copy link
Copy Markdown
Contributor Author

This PR contributes to the full implementation of the rules_hdl migration. Compared to the previous version, this update enhances the BCR smoke tests and resolves dependency issues. Additionally, I have configured a monthly CI workflow to automatically fetch and merge updates from the upstream repository. I look forward to any feedback from the reviewers. ❤️

@MrAMS MrAMS marked this pull request as ready for review December 12, 2025 16:24

@UebelAndre UebelAndre left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This thread must first be resolved: hdl/bazel_rules_hdl#428 (comment)

@github-actions

github-actions Bot commented Feb 9, 2026

Copy link
Copy Markdown
Contributor

This PR has been automatically marked as stale because it has not had any activity for 30 days. It will be closed in 14 days if no further activity occurs. Please comment on this PR to keep it open, or ask @bazelbuild/bcr-maintainers to add the not stale label if it's still relevant.

@github-actions github-actions Bot added the stale Issues or PRs that are stale (no activity for 30 days) label Feb 9, 2026
@MrAMS MrAMS closed this Feb 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stale Issues or PRs that are stale (no activity for 30 days)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants