Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add new release repositories #539

Closed
1 task
SteveMacenski opened this issue Jun 5, 2024 · 3 comments · Fixed by #550
Closed
1 task

Add new release repositories #539

SteveMacenski opened this issue Jun 5, 2024 · 3 comments · Fixed by #550

Comments

@SteveMacenski
Copy link
Member

@SteveMacenski
Copy link
Member Author

SteveMacenski commented Jun 26, 2024

@nuclearsandwich how should I go about moving that existing release repo over to this org - should I add you to the existing repo to do the transfer or should I myself? I just don’t want to make a move like that without the OK and that I have the appropriate permissions.

@nuclearsandwich
Copy link
Collaborator

should I add you to the existing repo to do the transfer or should I myself? I just don’t want to make a move like that without the OK and that I have the appropriate permissions.

Thanks for checking in. We generally don't bother with transferring release repositories. I usually use a mirror clone and push to update the ros2-gbp repository.

git clone --mirror <previous release repo>
git remote add ros2-gbp [email protected]:ros2-gbp/$(basename pwd)
git push --mirror ros2-gbp

I also recommend archiving the original release repo so that the artifacts remain available but the repository is not accidentally used instead of the ros2-gbp one.

@SteveMacenski
Copy link
Member Author

Done. Should I manually update the rosdistro file or does part of the automation here do that? https://github.com/ros/rosdistro/blob/master/rolling/distribution.yaml#L3840-L3854

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

Successfully merging a pull request may close this issue.

2 participants