Lack of сlear update flow to new version about jekyll-theme-chirpy HOT 4 CLOSED

Have you checked the Upgrade Guide?

It says that the preferred option is to use the starter project, so all you have to worry about is which version number to use.

If you went with the fork option, then you have to deal with all the possible merge conflicts and everything like a typical development procedure. "Development" is a crucial part here, because this option means that you are developing, not just using a tool.

Typically, I would say that if you go with the starter option and just maintain the version of the gem you want to use, and avoid adding any custom logic, then you should be fine in most cases. Otherwise, you are acting like a developer and are responsible for fixing any problems that may arise. This is especially true considering that we are talking about a theme, not a core instrument.

I don't disagree with your suggestion, but I'm not sure what exactly could be done to automate development.

from jekyll-theme-chirpy.

Absolutely, my apologies for missing that in the documentation. Thanks for the clarification; it resolves my query completely. I appreciate your patience and guidance.

from jekyll-theme-chirpy.

No worries at all @a-khakimov
It's good to know your issue is resolved 👍
Happy coding 😊

from jekyll-theme-chirpy.

I think if you can keep a branch for all fork option users, where all necessary files have been deleted already, then such merge conflicts might be gone.

Just some rough idea, and I might be able to test and prove it.

from jekyll-theme-chirpy.