Add --force-push flag in rill deploy to force push changes for rill managed repos

[k-anshul]

https://linear.app/rilldata/issue/PLAT-489/change-to-rill-deploy-commands

Checklist:

• Covered by tests
• Ran it and it works as intended
• Reviewed the diff before requesting a review
• Checked for unhandled edge cases
• Linked the issues it closes
• Checked if the docs need to be updated. If so, create a separate Linear DOCS issue
• Intend to cherry-pick into the release branch
• I'm proud of this work!

[nishantmonu51]

@codex: review

[nishantmonu51]

LGTM, overall.

[nishantmonu51]

well, Any specific reason for not allowing it for maanged repos ? If they are using a non-protected branch ideally we can do a force push, right ? If its a protected branch, it fails when doing the force push..

[k-anshul]

For self hosted repos a user can still force their changes but it is done using MergeWithOursStrategy to avoid force push and let user recover changes. This was intentionally done sometime back :

rill/cli/pkg/cmdutil/helper.go

Lines 641 to 642 in 634efc7

	// Instead of a force push, we do a merge with favourLocal=true to ensure we don't lose history.
	// This is not equivalent to a force push but is safer for users.

For managed repos most users have their changes backed in other git providers so it is okay to do a force push for them if they choose to do so.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 058babcb27

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[nishantmonu51]

LGTM, 👍