Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Native php token #35

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Native php token #35

wants to merge 1 commit into from

Conversation

keradus
Copy link
Owner

@keradus keradus commented Mar 3, 2022

No description provided.

@kubawerlos
Copy link

Seems like a step forward 👍🏼

I wonder if we can reasonable measure how the changes affects performance, in case we decrease it heavily by accident.
Also maybe we can have all these behind some feature flag in case we want to withdraw from the idea.

Or maybe both doubts don't make sense and we are sure this is the way to go 😄

@keradus
Copy link
Owner Author

keradus commented Mar 23, 2022

@github-actions
Copy link

github-actions bot commented Jun 8, 2023

Since this pull request has not had any activity within the last 90 days, I have marked it as stale.

I will close it if no further activity occurs within the next 14 days.

Please keep your branch up-to-date by rebasing it when main branch is ahead of it, thanks in advance!

@keradus
Copy link
Owner Author

keradus commented Jun 8, 2023

go away bot

@github-actions github-actions bot closed this Apr 4, 2024
@keradus keradus reopened this Apr 5, 2024
Repository owner deleted a comment from github-actions bot Apr 5, 2024
Repository owner deleted a comment from github-actions bot Apr 5, 2024
Repository owner deleted a comment from github-actions bot Apr 5, 2024
Repository owner deleted a comment from github-actions bot Apr 5, 2024
Copy link

github-actions bot commented Aug 4, 2024

Since this pull request has not had any activity within the last 90 days, I have marked it as stale.

The purpose of this action is to enforce backlog review once in a while. This is mostly for maintainers and helps with keeping repository in good condition, because stale issues and PRs can accumulate over time and make it harder for others to find relevant information. It is also possible that some changes has been made to the repo already, and issue or PR became outdated, but wasn't closed for some reason. This action helps with periodic review and closing of such stale items in automated way.

You may let maintainers handle this or verify current relevancy by yourself, to help with re-triage. Any activity will remove stale label so it won't be automatically closed at this point.

I will close it if no further activity occurs within the next 14 days.

Please keep your branch up-to-date by rebasing it when main branch is ahead of it, thanks in advance!

Copy link

The fact this was automatically closed doesn't mean that the idea got rejected - it simply didn't get any priority for way too long to keep it open. If you're still interested in this, please let as know, we can consider re-opening it. When it comes to pull requests it may be better to create new one, on top of main branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants