Skip to content
New issue

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

Ignore files when exporting package #215

Merged
merged 1 commit into from
Jan 3, 2021

Conversation

simonschaufi
Copy link
Contributor

This commit is part of a campaign to reduce the amount of data transferred to save global bandwidth and reduce the amount of CO2. See Codeception/Codeception#5527 for more info.

This commit is part of a campaign to reduce the amount of data transferred to save global bandwidth and reduce the amount of CO2. See Codeception/Codeception#5527 for more info.
@TomasVotruba
Copy link
Contributor

Hi, cool idea, thanks for contribution 👍

If you want, you can check other repositories I help to maintain for similar CO2 cleanup :)

@TomasVotruba TomasVotruba merged commit c28f1ee into cpliakas:master Jan 3, 2021
@simonschaufi simonschaufi deleted the gitattributes branch January 3, 2021 14:02
@simonschaufi
Copy link
Contributor Author

simonschaufi commented Jan 3, 2021

@TomasVotruba could you please delete the last git tag and prefix it with a v? Somehow my composer update doesn't get the new release.

composer update: Installing cpliakas/git-wrapper (v3.0.3): Extracting archive

@TomasVotruba
Copy link
Contributor

TomasVotruba commented Jan 3, 2021

It's on porpuse to keep using only numbers for versions. The v should be ignored in this case.

This works fine:

composer require cpliakas/git-wrapper

image

Try to cleaning composer cache, removing composer.lock and requiring the ^3.1 in composer.json explicitly.

@simonschaufi
Copy link
Contributor Author

simonschaufi commented Jan 3, 2021

My fault, I saw that the new version require php 7.3 and i had it set to 7.2. Now it works 🎉 Should be mentioned in the release notes ;)

@TomasVotruba
Copy link
Contributor

No problem :)

I only have time for such release notes: v3.0.3...master

Contributions of better version is welcomed :)

@simonschaufi
Copy link
Contributor Author

@TomasVotruba just make a release with a git tag and write a couple of things that have changed. That would be great

@TomasVotruba
Copy link
Contributor

Well, nothing relevant has changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants