jnode-revisited.github.io with Gitflow, GitHub flow or any-flow?

[ghost]

Hi everyone, hi @tripleo1.

Concept

I would like to add "my-flow" in jnode-revisited.github.io.

FAQ

• a) But... why discuss flow in Git or GitHub or jnode-revisited.github.io? b) or why add 'my-flow' in jnod-revisited.github.io?

  1. In any open source project there are always improvements, fixes, releases, bugs, features etc. So, discussing the best way of working always appears at the beginning of an open source project or over the years with the collaboration of several people.
  2. So... an open source project to avoid any internal or external communication failure, or to improve transparency in communication and at work or for 'better security' some open source project add some "flow" or "workflow" to process of work.

• c) what is my flow in Git or GitHub? d) but... what is "my-flow" in jnode-revisited.github.io? e) but... why separate code into separate branches?
  I separated the code into 3 parts, each part is a separate branch: 'vercel', 'netlify', 'github-pages' in github/jnode-revisited/jnode-revisited.github.io... this is "my-flow" in jnode-revisited.github.io... because:

  • "Greater control, security, auditability."
  • each separate branch is for each hosting independently - it is only necessary to choose the branch in the hosting and deploy it (even if there are several different hosts)
  • if any page crashes due to a traffic limit on the free hosting, chances are another page won't crash (unless somehow there's some traffic cap for all pages too, in which case that's the worst possible scenario)
  • another argument is that usually in each open project or page we have a different target audience, so thinking about a branch for each hosting is something possibly interesting in a small or large project

Please, see this concept.

image-description: As we can see in the image of the architecture, we have 3 different hosting options for each target audience and which have - or may have a traffic limit or not.

• f) are there alternatives to your flow? (are there alternatives to Gitflow?)
  Yes there is an alternative to Gitflow, this alternative some call 'GitHub flow', 'GitLab flow', 'Trunk-based development' or 'any flow' - sometimes each open project has a workflow that differs from GitHub-flow and Gitflow or GitLab flow and or Trunk-based development etc.

• g) and what is the difference between GitHubflow and Gitflow?

  1. Gitflow is an alternative Git branching model that involves the use of feature branches and multiple primary branches. It was first published and made popular by Vincent Driessen at nvie. Compared to trunk-based development, Gitflow has numerous, longer-lived branches and larger commits.
  2. GitHub Flow is a simpler alternative to GitFlow ideal for smaller teams as they don't need to manage multiple versions. Unlike GitFlow, this model doesn't have release branches because your deployment to production happens every day. There are two types of branches involved in this flow, the master branch, and the feature branch.
  3. Github Flow focuses on Agile principles and so it is a fast and streamlined branching strategy with short production cycles and frequent releases. This strategy also allows for fast feedback loops so that teams can quickly identify issues and resolve them.

Please, see this concept.

concept: Gitflow

concept: GitHubflow

FAQ - part 2

How can I clone separate branches?

Here below is a list of commands to clone the separate branch.

• git clone -b vercel https://github.com/jnode-revisited/jnode-revisited.github.io.git - if you only want to download the technical documentation of jnode-revisited for... Vercel
• git clone -b github-pages https://github.com/jnode-revisited/jnode-revisited.github.io.git- if you only want to download the homepage(landing-page) of jnode-revisited for... GitHub-Pages
• git clone -b netlify https://github.com/jnode-revisited/jnode-revisited.github.io.git - if you only want to download the hugo-website-index of jnode-revisited for... Netlify

How can I select separate branch in GitHub pages?

image-description As we can see in the image, we can see that there is a branch: 'main', 'vercel', 'github-pages'. We can decide which of these branches will be hosted on GitHub-Pages. Note: In that sense, just select the technical documentation with the vercel branch option... and... docsify.js works on GitHub-Pages.

or here too

What advice could you give to avoid any problems for repository: jnode-revisited?

I kindly ask that no one merge the branch: 'vercel', 'github-pages' and 'netlify' in 'main'.

How did you manage to create separate branches?

I sent a separate pull request for each code. Every update I make will be on a separate branch.

Could you demonstrate the difference between each branch? demo?

image-description: As we can see in the image, we have a branch called 'github-pages' for homepage in github/jnode-revisited/jnode-revisited.github.io

How I added my-flow in jnode-revisited.github.io?

image-description: As we can see in the image, there are several branches: 'vercel', 'netlify', 'github-pages' etc.

my-flow: 'vercel' & jnode-revisited.github.io

image-description: As we can see in the image, we have a branch called 'vercel' for technical documentation.

"my-flow": 'github-pages' & jnode-revisited.github.io

"my-flow": 'netlify' & jnode-revisited.github.io

"my-flow" & pull request

question/feedback

What do you think of this idea? it makes sense?