Change Details

This should ease further add-forge-now scheduling, something along those line should be enough to fetch and schedule the forge we just listed: ``` swh scheduler origin \ add-forge-now \ --visit-type git \ (--visit-type svn \ # you got the gist, imagine here that gitea list svn stuff ;) --lister-name gitea \ --lister-instance-name git.afpy.org \ ( --only-disabled ) # for staging ``` Related to https://gitlab.softwareheritage.org/infra/sysadm-environment/-/issues/4674

This should ease scheduling the first visits for add-forge-now request. The following would be enough to fetch and schedule the forge just listed (be it in production or staging): ``` swh scheduler add-forge-now \ schedule-first-visits \ --visit-type git \ (--visit-type svn \ # if a lister lists multiple kinds of visit, we can mention it ) --lister-name gitea \ --lister-instance-name git.afpy.org \ ( --production | --staging ) # to list only enabled | disabled origins ``` Related to https://gitlab.softwareheritage.org/infra/sysadm-environment/-/issues/4674

This should ease further add-forge-now scheduling, something along those line should bescheduling the first visits for add-forge-now request. The following would be enough to fetch and schedule the forge just listed (be it in enough to fetch and schedule the forge we just listed:production or staging): ``` swh scheduler origin \add-forge-now \ add-forge-now \schedule-first-visits \ --visit-type git \ (--visit-type svn \ # you got the gistif a lister lists multiple kinds of visit, imagine here that gitea list svn stuff ;we can mention it ) --lister-name gitea \ --lister-instance-name git.afpy.org \ ( --only-disabled--production | --staging ) # for stagingto list only enabled | disabled origins ``` Related to https://gitlab.softwareheritage.org/infra/sysadm-environment/-/issues/4674