magento / magento/community-features
Make magento/product-community-edition available on GitHub
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 46
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Currently is not possible to see the differences between versions for magento/product-community-edition composer virtual package (and enterprise as well). For a custom project, requiring magento/product-community-edition directly is not viable because unwanted packages are added by it, so instead we copy the require section into our own composer.json and remove what we need. But this quite an extensive task to get them every time a new version is released, since several modules have their versions bumped.
Preconditions
None
Steps to reproduce
None
Expected result
- Have
magento/product-community-edition'scomposer.jsondefinition available on GitHub, with all applicable tags, so we can diff thecomposer.jsonbetween all the released versions; - Bonus: have
magento/product-community-editionavailable on Packagist.org; - Bonus: have
magento/product-enterprise-editionavailable on GitHub (and/or Packagist.org) if applicable/allowed;
Actual result
magento/product-community-edition definition is not available anywhere public.
Original Report: https://github.com/magento/magento2/issues/13749 by @kassner
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing community-features issue #62 and the linked original report #13749 to understand the package publication constraints. Done means the community package definition is publicly available with applicable release tags for version diffs; the enterprise and Packagist requests are bonus scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100