Magento 2.4.1 : composer install : lost files ./.github ./.gitignore

[tales-desde-mileto]

Preconditions (*)

1. 2.4.1

Steps to reproduce (*)

1. composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition=2.4.1

Expected result (*)

1. The files .gitignore should be in root directory

Actual result (*)

1. This files: .gitignore are not in root directory

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• < ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ > Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @tales-desde-mileto. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[hostep]

The directory .github should not be installed, that was a bug and is fixed now, which is good!

As for the .gitignore file, that is unexpected indeed, not sure what's going on with that file ...

[NetStorm84]

I can confirm this issue. I have just installed 2.4.1 via composer an the .gitignore file was missing.

[sdzhepa]

Hello @tales-desde-mileto @hostep @NetStorm84

Thank you for report and collaboration.

I just received a response from the Magneto team responsible for that
Quote:

it is expected behavior. but it looks like people need it and use it. We will include it into next release

[magento-engcom-team]

✅ Confirmed by @sdzhepa
Thank you for verifying the issue. Based on the provided information internal tickets MC-38512 were created

Issue Available: @sdzhepa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[nkajic]

Should it be included as .gitignore or .gitignore.sample that is the question. If we include it without .sample suffix it will be overwritten after each composer install. 🤔

[hostep]

it is expected behavior. but it looks like people need it and use it. We will include it into next release

So that's why they now also removed it from 2.3.6-p1 (which will be released on 9 February)? Only to add it back in 2.3.7 (11 May)? 😛
This is kind of a silly move (even though I think I understand the underlying process which causes this).