This repository has been archived by the owner on Sep 5, 2020. It is now read-only.
docs: mark project as deprecated #58
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The project lives on in spirit in the form of liferay-npm-tools and specifically the liferay-npm-scripts package: https://github.com/liferay/liferay-npm-tools/tree/master/packages/liferay-npm-scripts
|
This is just house-keeping, so merging. |
|
Related internal ticket to mark repo as archived: https://issues.liferay.com/browse/IS-776 |
This was referenced Sep 4, 2020
Closed
Closed
Closed
|
😢 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The project lives on in spirit in the form of liferay-npm-tools and specifically the liferay-npm-scripts package:
https://github.com/liferay/liferay-npm-tools/tree/master/packages/liferay-npm-scripts
Will reach out to IT to actually archive the project because: (a) We aren't going to do any further development on this repo; (b) Even if we wanted to, @natecavanaugh is the sole owner of the NPM package and he's no longer with us; and (c) Archiving should stop new issues and PRs being created by bots (like this one).