Skip to content

Conversation

@pjreiniger
Copy link
Contributor

These are the scripts I've been using to sync between mostrobotpy and here. I debated putting it in the "source of truth" that is mostrobotpy , but I think it makes more sense here since it already has bazel set up, and I've also recently added the ability to sync the commands-v2 repository, so having it all in one copybara script makes sense.

This includes a helper python script to make it a little bit easier to run.

@pjreiniger pjreiniger requested a review from a team as a code owner November 13, 2025 01:15
@github-actions github-actions bot added the 2027 2027 target label Nov 13, 2025
core.workflow(
name = "commandsv2_to_allwpilib",
origin = git.origin(
url = "https://github.com/robotpy/robotpy-commands-v2.git",
Copy link
Member

Choose a reason for hiding this comment

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

Is there a good reason to maintain the robotpy-commands-v2 repo in the first place? It's pure-Python, so we could just build and publish it from here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I guess that is a good question. IT shouldn't be hard to add the wheel creation and figure out how to get it pushed to pypi. I think that should be a @virtuald decision though

Copy link
Member

Choose a reason for hiding this comment

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

There's two separate problems with pushing it from here.

  • One is that @PeterJohnson often slides the tag, and PyPI won't allow you to overwrite a PyPI artifact. That part of the current allwpilib workflow would need to change.
  • Historically it's been useful to be able to fix python issues out-of-band from normal wpilib releases. Perhaps this is less important if everything is being built/maintained along with everything else.

Copy link
Member

Choose a reason for hiding this comment

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

I was thinking we could make it a manually triggered workflow (workflow_dispatch). Alternatively we could have that workflow trigger on a different tag naming convention. Either way seems like a solvable problem.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Either way I say punt kill the source of truth for commandsv-2 while the dust settles on this mirroring effort

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

2027 2027 target

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants