opendevreview | OpenStack Proposal Bot proposed openstack/project-config master: Normalize projects.yaml https://review.opendev.org/c/openstack/project-config/+/899446 | 03:28 |
---|---|---|
opendevreview | yatin proposed openstack/project-config master: Update Grafana dasboard for Neutron master https://review.opendev.org/c/openstack/project-config/+/898836 | 04:49 |
opendevreview | yatin proposed openstack/project-config master: Update Grafana dashboard for Neutron master https://review.opendev.org/c/openstack/project-config/+/898836 | 04:51 |
jovial | We've got a branch that is no longer used: https://opendev.org/openstack/kayobe/src/branch/feature/zookeeper. How can I get it removed? | 09:00 |
frickler | jovial: mnasiadka: is looks like the branch may have been part of the initial import from stackhpc into opendev? because from the ACLs I can't see how it would have been created within opendev/gerrit | 09:25 |
mnasiadka | frickler: yes, that's part of the initial import | 09:25 |
frickler | so usually this should have been handled before approving the import. I'll check with other infra-root whether we can just delete the branch in gerrit as a one-off | 09:29 |
frickler | mnasiadka: just to confirm, you want the branch to completely disappear so it gets pruned from the git tree, no tag to keep a reference? | 09:30 |
mnasiadka | frickler: no tag, it's not needed anymore (I guess it wasn't needed intially) | 09:31 |
mmagr | Hi guys, can somebody please check review.opendev.org/c/openstack/requirements/+/898699 ? This patch should unblock telemetry patches. | 10:29 |
frickler | mmagr: not everyone may identify as "guys", it would be nice to choose a more generic addressing. also commented on the patch referencing the discussion that already happened in #openstack-requirements, where that patch would be more ontopic | 11:26 |
mmagr | frickler: ah, sorry about that | 11:27 |
mmagr | frickler: I wasn't aware of that discussion | 11:28 |
frickler | mmagr: see https://meetings.opendev.org/irclogs/%23openstack-requirements/%23openstack-requirements.2023-10-20.log.html and the following days | 11:33 |
mmagr | frickler: ack, thank you | 11:39 |
opendevreview | Merged openstack/project-config master: Normalize projects.yaml https://review.opendev.org/c/openstack/project-config/+/899446 | 12:29 |
clarkb | frickler: we have done those in the past, but I thik the release team can do that as well? | 14:06 |
clarkb | those == branch deletions | 14:06 |
frickler | clarkb: release team said that feature branches are out of scope for them | 14:08 |
clarkb | I strongly disagree on that one | 14:09 |
clarkb | the release team manages branches in opesntack projects. Any branch in an openstack project is within scope | 14:09 |
clarkb | if they don't then we should just let people branch and tag without intervention... | 14:09 |
frickler | well in this special case the branch results from an unclean import from github, which may be a special case. but feel free to pick up the earlier discussion in the release channel, I'll wait for the result of that | 14:11 |
clarkb | considering this is a single branch that was due to an import I don't have a problem with someone doing it though. Its straightfoward though may need to temporarily promote your normal gerrit account to admin rather than your admin account if there isn't a good cli comamnd for it | 14:11 |
clarkb | I think the cli approach is to do a git push but that requires project creator perms. Rather than perms given by the admin interfaces in the web ui | 14:11 |
clarkb | ya looks like there is a create branch ssh command but no delete branch equivalent | 14:16 |
fungi | explicit delete can be done through the rest api (and the webui of course) | 14:16 |
clarkb | this means we either need to promote our administrative account to project creator then push the special empty ref thing to delete a git branch. Or promote our regular user to admin temporarily and perform the action via the web ui | 14:16 |
clarkb | fungi: ya the problem is sorting out perms against what you can do and ithink those are the two options | 14:17 |
fungi | agreed, what i've done in the past is add my normal user to project bootstrappers temporarily, perform the operation, then take it back out of the group | 14:17 |
clarkb | noe you only need boostrappers if doing the git push method | 14:18 |
clarkb | I don't know that bootstrappers will work for the web ui method | 14:18 |
fungi | ah, right, administrators | 14:18 |
clarkb | since the perms for that are separate iirc (owner which is implied by admin vs force push ref which is bootstrapper) | 14:18 |
opendevreview | Joshua Reed proposed openstack/project-config master: Add starlingx/app-gen-tool https://review.opendev.org/c/openstack/project-config/+/899487 | 15:14 |
opendevreview | Joshua Reed proposed openstack/project-config master: Add starlingx/app-gen-tool https://review.opendev.org/c/openstack/project-config/+/899487 | 15:42 |
opendevreview | Merged openstack/project-config master: Add starlingx/app-gen-tool https://review.opendev.org/c/openstack/project-config/+/899487 | 19:32 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!