This repository was archived by the owner on Sep 23, 2021. It is now read-only.
Updated: Moved extension internals into repostitory root #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…sion checkout and use
nlescure
added a commit
that referenced
this pull request
Sep 24, 2014
…s-into-repo-root Updated: Moved extension internals into repostitory root
Owner
|
Thank you ! |
brookinsconsulting
deleted the
relocate-extension-files-into-repo-root
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
In this pull request we have moved the extension internals into the repository root to make the checkout process work cleanly by default without extra work or symlinks.
Details
We recently had the need to run cronjobs via the admin and found your extension. Thank you!
We were pleased to find again your extension updated to work with the latest community release. The extension worked perfectly for us the first time with minimal configuration setup!
We were however disappointed to find that the extension has not been touched for 3 years.
We hope to help improve this with our first pull request!
We think that the extension internals belong in the repository root like almost every other ezpublish extension on GitHub (from eZ Systems, 3rd Party Vendors, Partners, Community Members, etc).
We have successfully had similar changes merged in the past by others in the eZ Community: dbteam/ezchangeclass#1
Closing
We think this pull request is important to help people be able to make quick use of the extension without needing to move the extension checked out around. Please let us know what you think.
Thank you for your continued support!
Cheers,
Brookins Consulting