Create ForbiddenHttpException.php #5
Conversation
Add Exception class with formal "Forbidden" name for 403
|
I've tagged 1.0.4 (no 1.0.3, since I noticed you already had one and I might as well try to make upgrades a little smoother). |
|
Sounds good to me. Anything in particular i should do in my fork? Pull the new tag? |
|
You could, and then use that in your project. The next step for publishing is to tell packagist that there's a new tag. I'll ask if I can get temporary publishing permissions but (unfortunately) no guarantee that will be done anytime soon. |
|
Go for it. i just signed up, so i might tinker with publishing mine as a replacement ... If i go forward with that, would this one need an update as abandoned and suggest mine? Or does packagist figure that out? |
|
It's been a while since I checked but I think it's all manual. The proper flow is to mark this package as deprecated on packagist, link to your fork from our README, and then archive this github repository. I think there's also another option I can ask about, where we add you as a maintainer to this repository, if that's something you'd be interested in...? |
|
Sure, if you have the time/interest to check into it, i'm willing. Thanks for your help with this.
…-------- Original Message --------
On May 2, 2023, 6:26 PM, Philip Cohn-Cort wrote:
It's been a while since I checked but I think it's all manual. The proper flow is to mark this package as deprecated on packagist, link to your fork from our README, and then archive this github repository.
I think there's also another option I can ask about, where we add you as a maintainer to this repository, if that's something you'd be interested in...?
—
Reply to this email directly, [view it on GitHub](#5 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AZENIMSVFLDWQYJIPRIMPCLXEGC2ZANCNFSM6AAAAAAXTSGYTQ).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Ok, I asked around, here's what I've got: the best path forward is for you to rename the namespace in your fork from 'Fuzz' to something else, and then you can go ahead and publish that on packagist. I'll add a message to this README linking to your fork and ask the org admin to archive the repository. |
|
Sounds like a plan. Thanks for following up. i appreciate the help.
Joe Theuerkauf
------- Original Message -------
…On Wednesday, May 3rd, 2023 at 5:40 PM, Philip Cohn-Cort ***@***.***> wrote:
Ok, I asked around, here's what I've got: the best path forward is for you to rename the namespace in your fork from 'Fuzz' to something else, and then you can go ahead and publish that on packagist.
I'll add a message to this README linking to your fork and ask the org admin to archive the repository.
—
Reply to this email directly, [view it on GitHub](#5 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AZENIMQYV6ICGMFBSJ7IMQTXELGE3ANCNFSM6AAAAAAXTSGYTQ).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
2 participants
Do-over-over of #3 and #4 (dedicated upstream branch)
Add Exception class with formal "Forbidden" name for 403