Deployment workflow enhancement

[neerajgangwar]

The deployment workflow currently uses two sets of branches:

1. For the project pages: master branch for the source code and gh-pages branch for the generated website.
2. For personal or organization webpages: source branch for the source code and gh-pages branch for the generated website.

Describe the solution you'd like
The above-mentioned behavior can be unified. For both use cases, master can be used for the source code and gh-pages can be used for deployment.

Describe alternatives you've considered
NA

Additional context
NA

[neerajgangwar]

I have raised a PR for this - #344.

[ivanpuhachov]

Hi! I was following the previous instruction and source branch, and after sync with upstream, github actions are no longer triggered. What should I do to fix it?

[ivanpuhachov]

Fixed it.

1. .github/workflows/deploy add source to the branches:

on:
  push:
    branches:
      - master
      - source

2. On Github - repo - Settings - Pages select gh-pages as a source branch – as it is written in current readme file. In old instructions it was master

[neerajgangwar]

Yes, this is one way. But the idea was to have source code in the master branch. So you could also do the following:

1. Delete the master branch.
2. Rename source to master.
3. Push all the future changes to master. The generated site will be pushed to gh-pages which should be selected as the source branch in publishing source.

[ivanpuhachov]

Got it, thank you!