#7398 Enable "Prevent creating new branches by git push" for all src.fedoraproject.org repositories
Closed: Fixed 4 years ago by kevin. Opened 5 years ago by tibbs.

  • Describe what you need us to do:

Perform magic needed to enable the "Prevent creating new branches by git push" hook for all package repositories on src.fedoraproject.org.

Newer pagure versions support a hook which prevent the creation of random (undeletable) git branches by git push. This was discussed in a thread on the devel list: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/3BDW5DGSKY7NHIL27VA2NH33A3ESEL2E/

There was some general agreement that it would be a good thing to enable this for every repository and let maintainers who really do wish to create branches by pushing them disable the hook manually. Since there is no API endpoint for enabling this hook, it would have to be done by some internal magic. (I am assuming this magic is actually possible; I do not know the internals.)

If this needs to go through FESCo first, I understand.

  • When do you need this? (YYYY/MM/DD)

No date

  • When is this no longer needed or useful? (YYYY/MM/DD)

No date

  • If we cannot complete your request, what is the impact?

Not much, really; all existing repos won't get this unless the maintainers go in and turn it on. I guess the default for new repositories would be something to discuss in a separate ticket.


Note: please make it disabled by default for forks.

Metadata Update from @pingou:
- Issue tagged with: src.fp.o

5 years ago

Metadata Update from @bowlofeggs:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

5 years ago

@pingou whats the status here? I think the options are landed, but we would need to go in and change all the existing repos (possibly in db?)

Pagure 5.9 will come with an API endpoint allowing to toggle API hooks.

We've planned to improve fedscm-admin for this, but at this stage I don't think we want to toggle every existing project out there.
If someone wants to work on it, I'll be happy to help with this. The first step will be to consult the devel list to validate the idea with everyone in the community.

With this, I think we may close this ticket

ok. Closing this ticket then.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

Login to comment on this ticket.

Metadata