Help with creating a github bug ticket.
Sorry guys, I dont normally make bug tickets. I have tried making one twice now and the gitbot keeps closing it down claiming there is not repo provided...
The first one that was true, but I couldn't seem to reopen it after updating it.
The second one, just auto closed even when provided.
It's not a big issue, and I could put in a hacky fix for myself, but I am just trying to assist in improvements.
Any advice on how I was meant to format it or how I go about consensually stepping on the gitbot?
Ticket: https://github.com/filamentphp/filament/issues/9517
GitHub
RelationManager toggaleable() with many columns renders offscreen....
Package filament/filament Package Version 3.0 Laravel Version 10.10 Livewire Version 3.1 PHP Version 8.1 Problem description Note: I had to make a new ticket as the gitbot closed my other one witho...
5 Replies
We can reopen it for you, but please provide a reproduction that doesn’t require sail.
In theory if you wanted to set up the DB and hosts yourself you totally can.
Sail is purley optional.
I can update the steps to say that it is optional if you like.
It just helps us if we can clone and go.
Reopened it for you.
Many thanks, I've updated the description.
Is there anything in the ticket that I can fix that would help me next time, so that gitbot doesnt just auto close it?
I don’t think so. This happened to someone else the other day too. Might be a bug in GitHub.