@nifadyev looks good, thanks, instead of merging into master, could you raise a PR against the dev branch please. We can merge in master when we've translated all the snippets to the new layout.

No problem, @satwikkansal. But in my opinion, it is more difficult to check and release huge PR than lots of small changes (so-called Trunk based development). I remember how I made a translation, and it was a pain to check it before merging.

But in my opinion, it is more difficult to check and release huge PR than lots of small changes (so-called Trunk based development). I remember how I made a translation, and it was a pain to check it before merging.

I agree, think of master branch as production code. And dev branch for staging code. That doesn't mean we have to merge long PRs into the dev branch, we can still merge code incrementally in dev branch. And when we've tested the dev branch for consistency, then we can merge dev into master, that one will be a big PR, yes, but there won't be anything as such that hasn't been reviewed already carefully, so we should be good. Let me know your thoughts.

Agreed, I will start making small PRs into dev branch. It would be awesome to create “parent” issue with good first issue label and track the progress there. I hope the label will attract some contributors.

Great, feel free to create the issue, I'll put the label 👍

Hey @satwikkansal , I don't have privileges to create new branches. Could you please create dev and delete irrelevant development and 3.0?

@nifadyev Done!

@satwikkansal , base branch has been changed to dev

@nifadyev there's one merge conflict, could you resolve it please, I'll merge post that!

@satwikkansal , thanks for noticing, the merge conflict has been resolved
Probably, markdownlint CI check should be optional for now since markdown files are not fully fixed yet

Yes, that's okay, I was wondering maybe we should increase the line length to 180, we can have separate linter for Python code and have line length set to a lower value there.

we should increase the line length to 180, we can have separate linter for Python code

Sure, will be changed in next PRs