[CIQ 6.12] Rebase v6.12.17

[PlaidCat]

Clean rebase, no config changes

Due to all the issues with GITHUB attempting to drag the ciq-6.12.y branch forward we're attempting something new where we create a new branch -next at the GKH version we're going to move to then rebase a branch from the current ciq-6.12.y and rebse that off the ciq-6.12.y-next after this gets approved and merged into ciq-6.12.y-next and we're ready to tag the release we'll actually rename the old ciq-6.12.y -> ciq-6.12.# then rename ciq-6.12.y.

Example

git branch ciq-6.12.y-next v6.12.18
git checkout ciq-6.12.y
git checkout -b {jmaple}_rebase_tmp_branch
git rebase ciq-6.12.y-next

../kernel-src-tree-tools/lt_rebase.sh

git push origin ciq-6.12.y-next {jmaple}_rebase_tmp_branch

• Create PR from {jmaple}_rebase_tmp_branch -> ciq-6.12.y-next
• PR Fixed up (as needed) and APPROVED

git checkout ciq-6.12.y-next 
git merge --ff-only {jmaple}_rebase_tmp_branch
git push origin ciq-6.12.y-next

# Taking `ciq_kernel-6.12.17-1` and only using the `6.12.17`
PAST_VERSION=$(git describe --tags --abbrev=0 | awk -F '-' '{print $2}')
git branch -m ciq-6.12.y $PAST_VERSION
git push origin :ciq-6.12.y $PAST_VERSION
git push origin -u  $PAST_VERSION


git branch -m ciq-6.12.y-next ciq-6.12.y
git push origin :ciq-6.12.y-next ciq-6.12.y
git push origin -u ciq-6.12.y

NEW_TAG=$(ciq_kernel-$(git describe --tags --abbrev=0 | sed 's/^.//g')-1)
git tag $NEW_TAG ciq-6.12.y
git push origin $NEW_TAG

[bmastbergen]

🥌