Allow us to block Copilot-generated issues (and PRs) from our own repositories on #github

https://github.com/orgs/community/discussions/159749

@ramsey @dseguy thanks! Let me know when you need sponsorship to be able to order more

@ramsey is it possible for you to ship a number of them to the Netherlands? So I can spread them here at user groups?

I'm delighted to announce that FrankenPHP is now officially supported by the @thephpf, that the project repository will be moved to the @php organization on GitHub, and that the collaboration between the PHP project, the Caddy web server, and @cooptilleuls will intensify even further!

PHP is kicking!

https://les-tilleuls.coop/en/blog/frankenphp-is-now-officially-supported-by-the-php-foundation

@danb @ramsey I do have the same issue, but I have this for years, in some projects... I don't know why

@digitalcraftsman

If you use the ramsey/composer-install GitHub Action with your projects, I have a question for you related to a new feature.

Please go vote in this poll and/or let me know what you think.

Cheers!

https://github.com/ramsey/composer-install/discussions/267

#PHP #Composer #GitHub

@ramsey thanks for sharing this, I did vote

@theseer @heiglandreas I can highly recommend orbstack on Mac. As it fixes all your network issues. You can even reach a container on its ip, like you can when you have a proper os 😋

@michael as far as I know, open provider does mostly B2B. But their services are reliable, I know a few Dutch companies that are using open provider. It's stable, their api is a bit messy, but that's not a real issue

@derickr @rob @heiglandreas

We just released phpdoc/ReflectionDocBlock which addresses an issue with multi line tag descriptions. In combination with phpstan/parser v2

#php

@nickstenning where are you looking? Any specific country?

@nickstenning @janl I see a match between two recent toots https://fosstodon.org/@sushee/114303632057425909

@Crell maybe I'm just too used to the known php syntax. But that already has its oddness, which makes it hard to learn and fully understand.

I'm a bit afraid that adding more "common sense" will make the language harder to use. Rather than that it adds more power.

Nevertheless, thank you very much for taking all the efforts to try to improve php for other people.

@Crell @ilutov sadly we both know the order or $needle and $haystack right?

I think there is no other way to fix this issue without breaking changes in php. The subject first approach is never gonna work in this context. And all extra syntax will not make it easier for developers to understand. I remember when working for the first time with a pipe operator (erlang if I remember correctly) was a pain. Because of all the extra concepts I had to learn.
Also the error handling was much of a pain

@Crell I'm not against the introduction of a pipe operator, and the choice of the operator symbol is clear. However I do not understand all the mangling with the parenthesis.
It would make sense to support 1 argument in pipes. And nothing more.

The suggestion to pipe to function names as strings doesn't also make it more clear what is happening. $a |> 'strtolower'

It feels like a lot of extra context parsing for the developers.
Maybe the key is, keep it simple?

@sebastian no problem, I will give it a shot later this week

@dgoosens yes, one tool is not always better. Video calls using Skype weren't that bad...

@sebastian if you want, I can create a pr for this? Also including caddy?

We just upgraded from @phpunit 10 to 12, without any issues. Thanks @sebastian and other contributors for making these upgrades so smooth!

#thankyou #php #foss

@Girgias thanks for explaining. And for all the work you do! It's awesome to see people working with dedication to improve php.