Skip to content
Docs
FAQ

Frequently Asked Questions

General

What is recommit?

recommit is an automated cherry-pick service that synchronizes your code changes across multiple branches. When you merge a Pull Request, recommit automatically cherry-picks the changes to all your configured target branches.

Which Git providers are supported?

Currently, recommit supports:

  • ✅ GitHub - Full support
  • 🔜 GitLab - Coming soon
  • 🔜 Bitbucket - Planned

Is recommit free?

recommit provides free basic functionality for one repository, no subscription required. For more repositories, see our pricing page.

Is my code secure?

Yes. recommit:

  • Never stores your source code
  • Only accesses repositories you explicitly authorize
  • Uses GitHub App permissions (not personal tokens)
  • All communication is encrypted (HTTPS/TLS)

Setup & Configuration

How do I get started?

  1. Sign in with GitHub at recommit.dev (opens in a new tab)
  2. Install the GitHub App
  3. Create a Roadmap with your target branches
  4. Link your repository and enable it

See our Get Started guide for detailed instructions.

What permissions does the GitHub App need?

recommit requires:

  • Repository contents (read/write) - To create branches and cherry-pick commits
  • Pull requests (read/write) - To create PRs for cherry-picked changes
  • Metadata (read) - To access basic repository information

Can I limit which repositories recommit can access?

Yes! During GitHub App installation, choose "Only select repositories" and pick specific repos. You can modify this anytime in your GitHub settings.

How do I add more repositories later?

  1. Go to GitHub → Settings → Applications → recommit
  2. Click "Configure"
  3. Add more repositories to the authorized list

Roadmaps

What is a Roadmap?

A Roadmap is a configuration template that defines which branches should receive cherry-picks and their processing order. For example, you can define changes to be cherry-picked in the order v1 → v2 → v3 → main. Cherry-picks will start from the branch after the source branch and process through to the end of the list.

Can I have multiple Roadmaps?

Yes! Create different Roadmaps for different purposes:

  • "Release Branches" for version branches
  • "LTS Support" for long-term support branches
  • "Security Backports" for security-critical branches

What does "Cherry-pick to Default Branch" mean?

When enabled, recommit will always include your repository's default branch (usually main) in cherry-picks, even if it's not listed in your branch configuration.

How do I change the branch order?

Edit your Roadmap and reorder the branches in the Branches field. Cherry-picks process from the source branch forward through the list.

Cherry-Pick Operations

When does cherry-pick trigger?

Cherry-picks trigger when a Pull Request is merged. Closing a PR without merging does not trigger cherry-picks.

What if a cherry-pick fails?

If a cherry-pick encounters conflicts, it will fail. You can:

  1. Check out the target branch locally
  2. Manually run git cherry-pick <commit-sha>
  3. Resolve conflicts
  4. Commit and push changes

You can also view failure reasons and status in the PR comments.

Can I skip cherry-pick for specific PRs?

Currently, there's no way to skip individual PRs. You can prevent cherry-picks by:

  • Temporarily disabling the repository before merging
  • Deselecting branches in the checklist before merging

Why didn't my PR get cherry-picked?

Check these common issues:

  1. Repository not enabled
  2. No Roadmap linked
  3. PR was closed, not merged
  4. Subscription expired
  5. Target branch doesn't exist

Can I manually trigger a cherry-pick?

Currently, cherry-picks only trigger automatically on PR merge. Manual trigger is planned for a future release.

Branches

What branch naming should I use?

recommit works with any branch naming convention:

  • Version branches: v1, v2, v3
  • Release branches: release-2026-q1
  • LTS branches: v5-lts

What if a target branch doesn't exist?

If a branch in your Roadmap doesn't exist in the repository, the cherry-pick for that branch will fail. The other branches will still be processed.

Can I use regex for branch matching?

Yes! Use the Regexp field in your Roadmap to match branches dynamically:

^release-.*$

This would match release-2026-q1, release-2025-q4, etc.

Billing & Subscription

How do I upgrade my plan?

Go to Console → Billing to view and manage your subscription.

Is there a free plan?

Yes! recommit provides free basic functionality for one repository permanently, no subscription required. For more repositories, subscribe to a paid plan.

What happens when my subscription expires?

  • Cherry-picks stop triggering
  • Existing history is retained for 90 days
  • Repository configurations are preserved
  • Reactivate anytime to resume

Can I get a refund?

See our billing terms for refund policy details.

Troubleshooting

Cherry-picks are slow

Cherry-picks are queued and processed sequentially per repository. During high load:

  • Tasks may take a few minutes to start
  • Complex repositories take longer
  • Check status in Cherry-Pick History

"Repository not found" error

This usually means:

  • Repository was removed from GitHub App authorization
  • Repository was deleted or renamed
  • Permissions were revoked

Re-authorize the repository in GitHub App settings.

"License invalid" error

Your subscription may have expired. Check billing status and renew if needed.

PRs not being created

Verify:

  1. Repository is enabled (not just linked)
  2. GitHub App has write permissions
  3. Target branches exist
  4. No branch protection blocking the bot

Feature Requests

Can I request a feature?

Yes! Contact us at support with your feature request.

Planned features

  • GitLab and Bitbucket support
  • Manual cherry-pick trigger
  • Slack/Discord notifications
  • Advanced conflict resolution
  • PR auto-merge option

Still Need Help?

If your question isn't answered here:

Security PatchesTroubleshooting