You have to be inside an angular-cli project in order to use the build command.

[WG-Com]

#i run this command 
git add *
git commit -m 'msg'
ng github-pages:deploy --message "Optional commit message"

then error to me :

#ng build
You have to be inside an angular-cli project in order to use the build command.

#ng g component hello
You have to be inside an angular-cli project in order to use the g command.

.....

[aciccarello]

Could you explain why this is unexpected? The cli needs to know how the project is configured.

[WG-Com]

which config file ?

steps:

ng new hello  -> ok
ng g component user -> ok
ng g component .... -> ok
ng serve -> ok
ng build -> ok

git add *
git commit -m 'msg'
ng github-pages:deploy --message "Optional commit message"  -> error => github token no permission
@here looks like delete my src/ dir and many other files , my src source code lost
ng build -> error:
You have to be inside an angular-cli project in order to use the build command.
........

[WG-Com]

happend again:

ng github-pages:deploy --message "msg"
(node:5689) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
Could not start watchman; falling back to NodeWatcher for file system events.
Visit http://ember-cli.com/user-guide/#watchman for more info.
Built project successfully. Stored in "dist/".
fs.js:95
      throw err;  // Forgot a callback but don't know where? Use NODE_DEBUG=fs
      ^

Error: ENOTEMPTY: directory not empty, rmdir 'next/dist/vendor/@angular/platform-browser/src/'

ng github-pages:deploy --message "msg"
ng build
You have to be inside an angular-cli project in order to use the build command.

[WG-Com]

now files in projects:(no src dir and config files now )

 >ls
404.html         dist             index.html       node_modules     tmp              vendor
app              favicon.ico      main.js          system-config.js typings

> ls dist
app              favicon.ico      index.html       main.js          system-config.js vendor

[filipesilva]

Hi @WG-Com, it seems like something went wrong in the deploy procedure, namely the error that you got: error => github token no permission.

Sometimes when this happens the repo is left on the gh-pages branch and you need to manually git checkout master. Your code is still there and safe.

I thought That I had picked fixed all scenarios where that happens but it seems there is at least one still. I'll try to fix it.

[kylecordes]

I realize this item is about a bug, but I'd like to suggest as alternative to "The cli needs to know how the project is configured": I think it would be quite possible and useful for a subset of the CLI functionality to work on "non-CLI" project. I was recently working on such a project, and wanted to scaffold a few components. CLI could have done 90% of it for me, if CLI was willing to run on non-CLI projects. It would need to skip a few bits here and there and assume some defaults, but still more useful than refusing to run. Obviously not a priority for today... but maybe eventually?

[filipesilva]

@kylecordes I'd prefer to not mix up the two things in this issue tbh, since the crux of the issue here is a bad error catcher that leaves the repo in the wrong branch and not the project restrictions. Happy to have another issue open for discussion though.

[kylecordes]

@filipesilva I made #1464 a feature request for the idea above.

[intellix]

Just a thought, how about serving directly from dist by using this: https://github.com/blog/2228-simpler-github-pages-publishing ?

[filipesilva]

@intellix I was thinking about that really... it would make the process a LOT simpler. Have you checked if it also works with user/organization pages? If so, I'm definitely partial to changing it that way.

The whole thing could be rewritten with a ng build --output-path=docs --base-url=projectName this way.

[intellix]

afraid I've never used it before, but they just posted a new blog post about it becoming even easier if it's relevant :) https://github.com/blog/2289-publishing-with-github-pages-now-as-easy-as-1-2-3