👍 add rebase:instant-drop action

[atusy]

With rebase:instant-drop action, users can instantly drop a
cursor-selected commit on GinLog.

Summary by CodeRabbit

• New Features
  • Added an instant drop option for Git rebase operations, allowing more flexible commit management during rebasing.

[coderabbitai]

Walkthrough

The pull request introduces a new rebase functionality in the denops/gin/action/rebase.ts file. Specifically, it adds the rebase:instant-drop command, which provides a new method for dropping commits during the rebase process. The new command allows users to quickly remove specific commits using the --onto option, enhancing the flexibility of commit management during rebasing.

Changes

File	Change Summary
denops/gin/action/rebase.ts	- Added doRebaseInstantDrop async function - Introduced rebase:instant-drop command - Implemented commit dropping mechanism with --onto option

Sequence Diagram

sequenceDiagram
    participant User
    participant VimPlugin
    participant GitCommand
    User->>VimPlugin: Trigger rebase:instant-drop
    VimPlugin->>VimPlugin: Gather rebase candidates
    VimPlugin->>GitCommand: Execute git rebase --onto
    GitCommand-->>VimPlugin: Perform instant drop of commit
    VimPlugin-->>User: Rebase completed

Loading

Poem

🐰 A Rabbit's Rebase Rhyme 🌿

With a hop and a git command's grace,
Commits drop in an instant's embrace
No more lingering, no more delay
Rebase magic sweeps troubles away
A coding dance, both swift and bright! 🚀

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 58.91%. Comparing base (8158189) to head (1842c2d).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #151   +/-   ##
=======================================
  Coverage   58.91%   58.91%           
=======================================
  Files          17       17           
  Lines         881      881           
  Branches      108      108           
=======================================
  Hits          519      519           
  Misses        362      362           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

denops/gin/action/rebase.ts (1)

85-106: Consider unifying error handling with other rebase commands.

Both doRebase and doRebaseInstantDrop lack a try/catch approach, whereas doRebaseInteractive includes one. It may be beneficial to unify the error handling pattern to ensure consistent user feedback and avoid potential unhandled errors. If the await approach is required here (as opposed to the async dispatch in doRebaseInteractive), you can still wrap it in a similar try/catch pattern and provide consistent messaging if an error occurs.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8158189 and 1842c2d.

📒 Files selected for processing (1)

• denops/gin/action/rebase.ts (2 hunks)

🔇 Additional comments (1)

denops/gin/action/rebase.ts (1)

28-34: Well-structured command definition.

This addition cleanly parallels the existing command definitions, maintaining consistency and readability in the init function. Good job!