Skip to content
This repository has been archived by the owner on Sep 23, 2021. It is now read-only.

Updated: Moved extension internals into repostitory root #1

Conversation

brookinsconsulting
Copy link
Contributor

  • Updated: Moved extension files into repository root for simpler extension checkout and use

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

nlescure added a commit that referenced this pull request Sep 24, 2014
…s-into-repo-root

Updated: Moved extension internals into repostitory root
@nlescure nlescure merged commit 03e4a9d into nlescure:master Sep 24, 2014
@nlescure
Copy link
Owner

Thank you !

@brookinsconsulting brookinsconsulting deleted the relocate-extension-files-into-repo-root branch September 24, 2014 11:50
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants