Howto rebase a source-git repo to a new upstream release

[jpopelka]

I have a source-git repo, which is not pushed anywhere, so I can rebase at will.
The thing is that rebasing it to a new upstream release is quite a few steps, so I'm wondering whether we should mention them in the docs

Ok, so what I'm doing in the source-git repo to rebase to a newly released version:

• git pull --rebase upstream main
• cd .distro/
• change Version: in spec to the newly released version
• download tarball: spectool -g *.spec
• sha512sum the-downloaded-tarball
• in source-git.yaml change the upstream_ref and sources path & url (even the tarball is not yet uploaded)

Now I can run source-git update-dist-git, which BTW works nicely.

Or perhaps have a new source-git rebase-to-version command to perform those steps?
Anyway, I'd start with discussing what are the supposed steps (above) and documenting them.

[stale]

This issue has been marked as stale because it hasn't seen any
activity for the last 60 days.

Stale issues are closed after 14 days, unless the label is removed
by a maintainer or someone comments on it.

This is done in order to ensure that open issues are still relevant.

Thank you for your contribution! 🦄 🚀 🤖

(Note: issues labeled with pinned or EPIC are
never marked as stale.)

[stale]

This issue has been marked as stale because it hasn't seen any
activity for the last 60 days.

Stale issues are closed after 14 days, unless the label is removed
by a maintainer or someone comments on it.

This is done in order to ensure that open issues are still relevant.

Thank you for your contribution! 🦄 🚀 🤖

(Note: issues labeled with pinned or EPIC are
never marked as stale.)

[stale]

This issue has been marked as stale because it hasn't seen any
activity for the last 60 days.

Stale issues are closed after 14 days, unless the label is removed
by a maintainer or someone comments on it.

This is done in order to ensure that open issues are still relevant.

Thank you for your contribution! 🦄 🚀 🤖

(Note: issues labeled with pinned or EPIC are
never marked as stale.)

[stale]

This issue has been marked as stale because it hasn't seen any
activity for the last 60 days.

Stale issues are closed after 14 days, unless the label is removed
by a maintainer or someone comments on it.

This is done in order to ensure that open issues are still relevant.

Thank you for your contribution! 🦄 🚀 🤖

(Note: issues labeled with pinned or EPIC are
never marked as stale.)

[stale]

This issue has been marked as stale because it hasn't seen any
activity for the last 60 days.

Stale issues are closed after 14 days, unless the label is removed
by a maintainer or someone comments on it.

This is done in order to ensure that open issues are still relevant.

Thank you for your contribution! 🦄 🚀 🤖

(Note: issues labeled with pinned or EPIC are
never marked as stale.)