@jreed:matrix.org | On the subject, does anyone in this chat have experience creating a new repository? I'm learning how to do it and its taking me a while. Am hoping someone with experience/time can help me speed it up. | 14:03 |
---|---|---|
@tcervi:matrix.org | jreed: Recently scott.little helped me to create the starlingx/virt repository: https://review.opendev.org/c/openstack/project-config/+/879076 | 15:44 |
This repo was basically a split from code that was previously inside stx/integ to a new place | ||
I don't remember if other changes were required on different repos, but I know that there was this topic to handle the manifest update and moving between repos: https://review.opendev.org/q/topic:virt-repo | ||
@jreed:matrix.org | > <@tcervi:matrix.org> jreed: Recently scott.little helped me to create the starlingx/virt repository: https://review.opendev.org/c/openstack/project-config/+/879076 | 15:59 |
> This repo was basically a split from code that was previously inside stx/integ to a new place | ||
> I don't remember if other changes were required on different repos, but I know that there was this topic to handle the manifest update and moving between repos: https://review.opendev.org/q/topic:virt-repo | ||
Scott has some script that will split out the repo to another one while preserving history. I'm waiting on him to make a github repo for me, and then he gave me a process to do what you're saying. | ||
@jreed:matrix.org | This is what I have: | 16:00 |
git clone https://opendev.org/openstack/project-config | ||
cd project-config | ||
git review -s | ||
Create a commit similar to this one ... https://review.opendev.org/c/openstack/project-config/+/887070 | ||
git review | ||
wait for it to be reviewed and merged ... then notify me as to who in initial set of core reviewers needs to be. | ||
populate your new git | ||
add it to the StarlingX manifest under .repo/manifests/ similar to ... https://review.opendev.org/c/starlingx/manifest/+/887169 | ||
git review | ||
@tcervi:matrix.org | we might have to re-evaluate documentation on how to create new stx repositories. it is not a common practice to create new repos, but should be as smooth as possible right? | 16:43 |
@jreed:matrix.org | This was pointed out to me but didn't seem like the whole picture. I did not find anything else. | 18:35 |
https://docs.opendev.org/opendev/infra-manual/latest/creators.html | ||
@jreed:matrix.org | I don't think new repos happen often, no. | 18:35 |
@jreed:matrix.org | * This is what I have: | 18:37 |
1. git clone https://opendev.org/openstack/project-config | ||
2. cd project-config | ||
3. git review -s | ||
4. Create a commit similar to this one ... - https://review.opendev.org/c/openstack/project-config/+/887070 | ||
5. git review | ||
6. wait for it to be reviewed and merged ... then notify me (scott little) as to who in initial set of core reviewers needs to be. | ||
7. populate your new git / make any necessary changes. | ||
8. add it to the StarlingX manifest under .repo/manifests/ similar to ... - https://review.opendev.org/c/starlingx/manifest/+/887169 | ||
git review |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!