Learn more about these different git repos.
Other Git URLs
PR in question: https://pagure.io/pungi/pull-request/1072
I reformatted the commit message and some code and merged the patch outside of Pagure. Then I pushed master branch to Pagure. The usual Merges: … is in the commit message. Pagure hook was enabled in the repo.
Merges: …
The commit now appears on master branch, but the PR is still opened and I see a Merge button that claims it can be merged via fast-forward. That's not even true, there's a merge conflict.
Ok, the issue is that pungi was one of the early projects created on pagure.io, which means it got a post-receive file instead of the symlink as a result it still running the old-type post-receive hook instead of the new one. I have a script to fix this but I don't want to run it while we're in freeze.
post-receive
In the meantime I fixed pungi manually so it works for you (please let me know if it is or not).
Sorry for the troubles
Metadata Update from @pingou: - Issue tagged with: bug
No problem, thank you. Once I get to test it I'll report the results.
Metadata Update from @pingou: - Issue assigned to pingou
Tested today, and it works correctly. Thank you very much!
A couple observations which are probably not problems:
git push
repr
remote: (u'*', u'commit 12f949fe84fc036c6211bce346f41fa61c1da8a9')
#pagure
Metadata Update from @lsedlar: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
the console output of git push showed Detailed log as output of repr, things like remote: (u'*', u'commit 12f949fe84fc036c6211bce346f41fa61c1da8a9')
Yes, we still have debugging turned on, we will turn it off in a near future :)
notification of the push appeared on #pagure IRC channel, probably because I referenced the PR by full URL.
The logic behind IRC notifications is quite simple so that could be it yes
Log in to comment on this ticket.