We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
figure out here https://www.drupal.org/project/automatic_updates/issues/3363937
What our case was
Result PHP file syncer: this file was not deleted on commit Rsync file syncer: this file was deleted on commit
We solved this by making the path relative but it seems like they should act the same way.
I chatted with @TravisCarden about this and the absolute path should only be used if it is in the source(stage in this case) directory.
The text was updated successfully, but these errors were encountered:
the absolute path should only be used if it is in the source(stage in this case) directory.
Right. But shouldn't \PhpTuf\ComposerStager\Infrastructure\Value\PathList\PathList::assertValidInput() validate that assumption?
\PhpTuf\ComposerStager\Infrastructure\Value\PathList\PathList::assertValidInput()
(See my write-up at https://www.drupal.org/project/automatic_updates/issues/3363937#comment-15087236.)
Sorry, something went wrong.
What do you think, @tedbow? Should we add validation to ensure relative paths?
No branches or pull requests
figure out here https://www.drupal.org/project/automatic_updates/issues/3363937
What our case was
Result
PHP file syncer: this file was not deleted on commit
Rsync file syncer: this file was deleted on commit
We solved this by making the path relative but it seems like they should act the same way.
I chatted with @TravisCarden about this and the absolute path should only be used if it is in the source(stage in this case) directory.
The text was updated successfully, but these errors were encountered: