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

Create phar artifacts from each build #11

Open
dktapps opened this issue Jun 1, 2023 · 3 comments
Open

Create phar artifacts from each build #11

dktapps opened this issue Jun 1, 2023 · 3 comments

Comments

@dktapps
Copy link
Member

dktapps commented Jun 1, 2023

No description provided.

@SOF3
Copy link
Member

SOF3 commented Jun 5, 2023

I can have a try for integrating this with pharynx (without any virions).

@dktapps
Copy link
Member Author

dktapps commented Jun 5, 2023

Is your intent to have pharynx supersede DevTools?

@SOF3
Copy link
Member

SOF3 commented Jun 6, 2023

I think it is ok. While the default usage of pharynx (using -i path/to/plugin) treats src as a source directory and executes processors on it (automatically converting source files to PSR-0 and erroring when namespace functions/constants/global statements are detected), the -f flag always works as a fallback approach if some users really don't want to use this feature.

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

No branches or pull requests

2 participants