#4248 All changes must be done via pull-requests from forks doesn't work
Closed: Fixed 4 years ago by jlanda. Opened 5 years ago by churchyard.

I have the option set for https://src.fedoraproject.org/rpms/python38 yet I've just pushed https://src.fedoraproject.org/rpms/python38/c/553fd279baf25122ce00ea8b4ae565a27a72c9d7?branch=master with:

$ git push 
Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 8 threads
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 554 bytes | 554.00 KiB/s, done.
Total 3 (delta 2), reused 0 (delta 0)
remote: Protected namespaces: ['rpms', 'modules', 'container']
remote: Blocking unspecified refs: False
remote: Blacklists: [<_sre.SRE_Pattern object at 0x7f35964817b0>]
remote: User: User: 232 - name churchyard
remote: User groups: set([u'modularity-wg', u'provenpackager', u'packager', u'python-sig'])
remote: Committer: True
remote: SIG memberships: set([])
remote: RCM: False
remote: Branch refs/heads/master is supported
remote: Protected namespaces: ['rpms', 'modules', 'container']
remote: Blocking unspecified refs: False
remote: Blacklists: [<_sre.SRE_Pattern object at 0x7f29d85247b0>]
remote: User: User: 232 - name churchyard
remote: User groups: set([u'modularity-wg', u'provenpackager', u'packager', u'python-sig'])
remote: Committer: True
remote: SIG memberships: set([])
remote: RCM: False
remote: Branch refs/heads/master is supported
remote: Emitting a message to the fedmsg bus.
remote: * Publishing information for 1 commits
remote: Sending to redis to log activity and send commit notification emails
remote: * Publishing information for 1 commits
remote:   - to web-hooks
To ssh://pkgs.fedoraproject.org/rpms/python38
   4aedf05..553fd27  master -> master

Metadata Update from @pingou:
- Issue tagged with: bug

5 years ago

If I recall rightly, provenpackagers override that behavior? You might not be allowed as the owner, but Dist-Git's provenpackager power may be letting you in.

If that is so, the option is useless. I trust myself and all the comaintainers to open PRs if we agree on the workflow. It's the provenpackagers that don't know we prefer PRs.

Metadata Update from @pingou:
- Issue assigned to pingou

4 years ago

Turns out that this was a plain bug, it's being fixed in: https://pagure.io/pagure-dist-git/pull-request/88

https://pagure.io/pagure-dist-git/pull-request/88 merged and in process to be deployed, so this is fixed

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

4 years ago

Login to comment on this ticket.

Metadata
Related Pull Requests
  • #88 Merged 4 years ago