-
Notifications
You must be signed in to change notification settings - Fork 4
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
Is this project alive? #9
Comments
I've extended the module with more powerful functions now. For instance: eloekset#8 Please respond to this issue if you're interested in pull requests to keep this repository in sync. |
Hi Sorry, I am not maintaining this anymore. I can add you as a collaborator if you like .. Or you can continue to work on your repo and publish your version to Nuget.. |
I think it’s easier if I can be a collaborator to this repository. At StackOverflow, I found a guide to make a fork the new main repository, but I’m not sure if that’s the best solution anyway. |
I have added you as a collaborate.. |
Tanks! I'll soon start merging my pull requests. |
I've started a develop branch in my forked repository (https://github.com/eloekset/publish-btdfBiztalkApplication) to continue developing this script to be used for BizTalk 2016. That branch contains all pull requests I've sent to this repository, which so far haven't been merged.
I've also used VSCode Format Document etc to follow the conventions of PSScriptAnalyzer in this PR: eloekset#4 Since it changes almost every line, I'll base all my future changes on my develop branch, which contains all these changes. I've intentionally haven't sent that PR to the main repository.
I just want to make the project owner aware of this, and there's no contact information to elangovana. So all my future development will be far off of the master branch in this repository.
The text was updated successfully, but these errors were encountered: