[jenkins-ci PATCH 0/3] Update various files after repo rename
All pushed as trivial. Andrea Bolognani (3): guests: Update README after repo rename git-publish: Update config after repo rename github: Update repo-lockdown config after repo rename .github/lockdown.yml | 6 +++--- .gitpublish | 2 +- guests/README.markdown | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) -- 2.25.2
Signed-off-by: Andrea Bolognani <abologna@redhat.com> --- guests/README.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guests/README.markdown b/guests/README.markdown index f225da7..ed9be06 100644 --- a/guests/README.markdown +++ b/guests/README.markdown @@ -80,7 +80,7 @@ you'll want to use the `libvirt_guest` variant of the plugin. To keep guests up to date over time, it's recommended to have an entry along the lines of - 0 0 * * * ~/libvirt-jenkins-ci/guests/lcitool update all all + 0 0 * * * ~/libvirt-ci/guests/lcitool update all all in your crontab. -- 2.25.2
Signed-off-by: Andrea Bolognani <abologna@redhat.com> --- .gitpublish | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.gitpublish b/.gitpublish index 331b33b..6cbfb62 100644 --- a/.gitpublish +++ b/.gitpublish @@ -1,4 +1,4 @@ [gitpublishprofile "default"] base = master to = libvir-list@redhat.com -prefix = libvirt-jenkins-ci PATCH +prefix = libvirt-ci PATCH -- 2.25.2
Signed-off-by: Andrea Bolognani <abologna@redhat.com> --- .github/lockdown.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/lockdown.yml b/.github/lockdown.yml index 1183cb8..5410b9f 100644 --- a/.github/lockdown.yml +++ b/.github/lockdown.yml @@ -15,7 +15,7 @@ issues: We kindly request that new issues are reported to - https://gitlab.com/libvirt/libvirt-jenkins-ci/-/issues/new + https://gitlab.com/libvirt/libvirt-ci/-/issues/new Thank you for your time and understanding. @@ -27,10 +27,10 @@ pulls: We kindly request that contributors fork the project at - https://gitlab.com/libvirt/libvirt-jenkins-ci/ + https://gitlab.com/libvirt/libvirt-ci/ push changes to the fork, and then open a new merge request at - https://gitlab.com/libvirt/libvirt-jenkins-ci/-/merge_requests/new + https://gitlab.com/libvirt/libvirt-ci/-/merge_requests/new Thank you for your time and understanding. -- 2.25.2
participants (1)
-
Andrea Bolognani