Skip to content

ng help shows No help entry for 'serve.run' and others. #3994

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

Closed
filipesilva opened this issue Jan 13, 2017 · 5 comments
Closed

ng help shows No help entry for 'serve.run' and others. #3994

filipesilva opened this issue Jan 13, 2017 · 5 comments
Labels
effort1: easy (hours) help wanted P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@filipesilva
Copy link
Contributor

While using 1.0.0-beta.25.5, running ng help shows No help entry for 'serve.run' and a couple of others in red. These entries should not be listed.

@filipesilva filipesilva added effort1: easy (hours) help wanted P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent labels Jan 13, 2017
@CarreraPHP
Copy link
Contributor

@filipesilva , #4001 & #3982 are 2 different PR for the same issue. in #4001 the issue is resolved using the ignore list and in #3982 the issue is resolved by excluding the '*.run.ts' files in the filter map.

Is there a way to know whether someone is working on a PR for an issue? I am searching for issues that can be reproduced in macOS Sierra for which i can make a PR but mostly end up find an already submitted one. At last, I comment in the issue referencing the PR that resolves the issue and again go back searching for an new issue. Can u suggest some easy to medium effort issues that can be resolved by new contributors like me.

@CarreraPHP
Copy link
Contributor

@hansl merged #3982

@filipesilva
Copy link
Contributor Author

Fixed by #3982

@filipesilva
Copy link
Contributor Author

Heya @CarreraPHP, I don't have a better way myself than to look at the PR list. A lot of the fixes are driven by users needing something fixed or wanting to help, and it's not coordinated.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
effort1: easy (hours) help wanted P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
Development

No branches or pull requests

2 participants