Learn more about these different git repos.
Other Git URLs
What is this Pull Requests GIT URLs address for? I pushed patch for koji to this URL for my fork and nothing happens.
Pull Requests GIT URLs
koji
I'd appreciate a small question marks next the the title explaining the details.
I would be the fourth repository mentioned at: https://docs.pagure.org/pagure/usage/index.html :)
Is it okay that I've just pushed my fork contents to it instead of metadata?
✗ git push patches Counting objects: 18463, done. Delta compression using up to 4 threads. Compressing objects: 100% (5197/5197), done. Writing objects: 100% (18463/18463), 4.31 MiB | 536.00 KiB/s, done. Total 18463 (delta 13242), reused 18419 (delta 13212) To ssh://pagure.io/requests/forks/abitrolly/koji.git
It is okay as in, it won't break anything but it won't serve any purposes either...
And which purposes it could serve? For example I submitted https://pagure.io/koji/pull-request/999 from my fork. What should happen to meta?
It stores the metadata of the pull-requests opened against a project. In this case the pull-request is on the koji project, so its pull-request repository has been updated with the metadata from your pull-request, while your pull-requests git repo is empty since the PR is opened against it.
I manually pushed koji code to my pull-requests repo. Does that mean that now nobody will be able to send me pull requests?
No, it does no harm but doesn't serve any purpose either :)
If I could just push to that URL to create PR without afterclicking the interface - that could be handy.
On Thu, Jul 26, 2018, 10:58 PM Pierre-YvesChibon pagure@pagure.io wrote:
pingou added a new comment to an issue you are following: `` I manually pushed koji code to my pull-requests repo. Does that mean that now nobody will be able to send me pull requests? No, it does no harm but doesn't serve any purpose either :) `` To reply, visit the link below or just reply to this email https://pagure.io/pagure/issue/3451
pingou added a new comment to an issue you are following: ``
No, it does no harm but doesn't serve any purpose either :) ``
To reply, visit the link below or just reply to this email https://pagure.io/pagure/issue/3451
That's not what it's meant for :)
I'm going to close this ticket, I believe the original question has been answered and while your last comment is an interesting idea (have a way to create a PR automatically from a git push), it deserves it own ticket rather than being buried here :)
Metadata Update from @pingou: - Issue close_status updated to: Invalid
Good resolution if this ticket would be to place hints on the interface or redirect to docs that could also include some use cases for this meta info.
On Fri, Jul 27, 2018, 3:47 PM Pierre-YvesChibon pagure@pagure.io wrote:
pingou added a new comment to an issue you are following: I'm going to close this ticket, I believe the original question has been answered and while your last comment is an interesting idea (have a way to create a PR automatically from a git push), it deserves it own ticket rather than being buried here :) To reply, visit the link below or just reply to this email https://pagure.io/pagure/issue/3451
pingou added a new comment to an issue you are following: I'm going to close this ticket, I believe the original question has been answered and while your last comment is an interesting idea (have a way to create a PR automatically from a git push), it deserves it own ticket rather than being buried here :)
if this ticket would be to place hints on the interface or redirect to docs that could also include some use cases for this meta info.
Then we should formulate things this way, no? Sorry if I'm not understanding this the way you thought I would.
Metadata Update from @pingou: - Issue status updated to: Open (was: Closed) - Issue tagged with: RFE, doc
Metadata Update from @pingou: - Issue assigned to pingou
Commit 13832f2 fixes this issue
Login to comment on this ticket.