Add guidelines for rebasing develop branch to release-v* to Kolibri Developer Documentation

[MisRob]

Summary

Especially before a new release, we sometimes guide contributors to rebase their pull request from develop to release-v* branch. There's a helpful guidance by @rtibbles in #11337 (comment):

• Make sure you have local versions of the Learning Equality develop branch and the Learning Equality release-v0.16.x branch and that they are both up to date - for the sake of the following, I will assume they are called develop and release-v0.16.x respectively.
• Locally, checkout your feature branch
• Run this rebase command: git rebase --onto release-v0.16.x develop this will rebase your current branch (your feature branch) onto release-v0.16.x, removing any commits that are already present in develop - so, if everything works as expected, it should keep your commit bugfix- birth year selction
• Once you have done that, you will need to force push to update your remote branch git push --force - if the remote branch is not set, then git should give you hints about how to push to the correct remote branch.

It'd be great to move it to Kolibri Developer Documentation as a new page in How To Guides.

release-v* should be used instead of release-v0.16.x so that the guidelines are applicable for any future releases.

Value Add

Efficiency

Guidance

• Documentation files location
• Documentation about updating documentation 🙃

[RISHIKESHk07]

hey @MisRob could i contribute to this

[MisRob]

Hi @RISHIKESHk07, yes, thank you

[Tweniee]

@MisRob i made the changes and created a PR, if any change needed please let me know
PR:#11509

[MisRob]

Thanks @Tweniee, I will have a look some time this week

[MisRob]

Closed by #11512