github-pages-deploy-action | 🚀 Automatically deploy your project to GitHub Pages | Continous Integration library

Besides the .env.local file, which is typically meant to contain things that are only needed locally, you can also use a file .env, .env.development, or .env.production. These files could then be checked in.

Your .env file can contain global defaults (e.g. some config). With the others, you can override configs specific to that environment.

As opposed to the .env.local file, the other three would typically be checked in.

See their docs for more info.

Easiest way is to use caching:

https://github.com/actions/cache

You can use hash of your file as a key.

When using composite actions, you have to specify shell.

In your case the problem is in this step, you need to add shell: bash here:

You are using an old version of that action. Perhaps try moving to v4 which handles some of these parameters differently. If you are pushing back to the same repository you do not even need to pass a token.

Other than that, I see two possible things to check:

1. You reference branch main in the first action but master in the second. Are these pointing to the same repository? If so, I'd think the branch names would be the same.

2. With the v3 component, the docs for ACCESS_TOKEN kind of imply you need to be using a generated Personal Access Token that you have stored in the secrets. That is what I used when using this action although I was pushing to a different repository so the was a must anyway.

I moved to v4 quite a while ago though.

I misunderstood the issue message, the problem was not duplicating the problem was the missed inner path passed in FOLDER in gh-pages YML settings

There was a hint in BUILD step

And one more thing: do not forget to get and add to GH your personal-access-token

You need to create a branch named development from master branch and set development branch as default branch in your repository settings.

This is because your gh-pages.yml files has BASE_BRANCH: development and BRANCH: master

According to the Angular doc, you have to make a copy of index.html and name it 404.html.

1. When the build is complete, make a copy of docs/index.html and name it docs/404.html.

bash ng build --prod --output-path docs --base-href//

You could add conditions to your steps and simply skip parts which aren't needed, see jobs..steps.if. As for what to check, github context is a goldmine of various data related to currently running workflow. For example

The problem is that React is purely a front-end framework. Everything that should be available directly in React is also available to your users to see. There's no way around this!

To really keep the secret private it has to be somewhere server side and not on the front-end. One way you could do this is make a "serverless function" (there are multiple generous free offers available on different services). Then you proxy through there, which basically means that:

1. Your react front-end fetches from your serverless function without any secret.
2. Your serverless function has the secret stored and does the same fetch on the actual service with secret.
3. Your serverless function can now return the response it got back to your React front-end.