Skip to content

Conversation

@TheDancingCode
Copy link

Closes #84

Copy link

@demurgos demurgos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, thanks.

@wiledal
Could we have this merged and published?

@TheDancingCode
Copy link
Author

@wiledal
Did you get a chance to look at this?

@TheDancingCode
Copy link
Author

Another friendly reminder.

@TheDancingCode
Copy link
Author

@wiledal or anyone else: any takers?

@petermonte
Copy link

Is this getting merged?

@rifler
Copy link

rifler commented Nov 29, 2018

friendly bump

@KenEucker
Copy link
Collaborator

KenEucker commented Nov 29, 2018

In light of the recent flatmap-stream drama, I feel that it is important to address and resolve issues like this in a timely manner instead of letting widely used packages like this fall to mismanagement. This PR is almost a year old.

Looking forward to fresh eyes on this.

@WordsofDefiance
Copy link

I will be removing gulp-include from my projects until this gets fixed.

@KenEucker
Copy link
Collaborator

friendly bump

@tsktech
Copy link

tsktech commented Apr 5, 2019

friendly bump

@KenEucker
Copy link
Collaborator

UPDATE:

I was able to have a conversation with the maintainer, @wiledal, and have agreed to provisionally join the github project to address the open pull requests. I am going to take some time to respond to the ones that seem the most important but I also urge anyone to make comments on any items that they feel are pertinent.

After I've approved and merged a few of the more important PRs (dependency updates), I will ask the community to pull down the master branch and test it before we publish a new version to NPM.

Thank you for your patience and understanding!

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.

8 participants