Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 835055
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 15, 20262026-05-15T04:45:55+00:00 2026-05-15T04:45:55+00:00

In this post , I found out that it was possible to create individual

  • 0

In this post, I found out that it was possible to create individual mappings for branch names so that pushing back to a central repository can be permanently mapped to a subtree, like:

  • git master branch name: foo
  • remote branch name: foo
  • git push origin foo on slave1 does the equivalent of git push origin foo:refs/slave1/foo

But the post implied that it’s not possible to do this on an automatic basis, e.g. specifying a wildcard map from refs/heads/* on the remote to refs/slave1/* on the master.

Well, is it possible?

I clone my repository in a ton of places, make changes on my devbox, and fetch those changes to the copy on the development server for testing. I end up making changes on the dev server and wanting to push them back, but I can’t push it with the same branch name because I have that branch checked out on the master. It would be nice to just configure the clone once to be smart about it.

If it’s not possible, this is a feature request and I’m pasting this URL to the git mailing list 🙂

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-15T04:45:55+00:00Added an answer on May 15, 2026 at 4:45 am

    I found the answer myself.

    git config --add remote.origin.push +refs/heads/*:refs/MACHINENAME/*

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.