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 6092221
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T12:25:03+00:00 2026-05-23T12:25:03+00:00

I usually develop new features of my codes in dedicated branches, then merge them

  • 0

I usually develop new features of my codes in dedicated branches, then merge them to master.

The problem with this is that after some time I have a lot of obsolete branches that are cluttering the github interface, where there might be instead branches which are actively developed.

Is there a way to archive them somehow, or should I just delete them, as the commits have already been merged?

  • 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-23T12:25:04+00:00Added an answer on May 23, 2026 at 12:25 pm

    If you have already merged branches and have no need to develop on them anymore, then it’s safe to delete them. You don’t loose any commit, as they have been merged and are now stored in master.

    I would only propose to leave branches you actively develop

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

Sidebar

Related Questions

usually i simply develop executable (.exe) files of my MATLAB codes by using this
In a Python system for which I develop, we usually have this module structure.
Usually I develop in Java but now I need to write an app that
I've noticed something that happens in every app i develop. It's usually not a
Every time I develop a new form that includes a textarea I have the
I know this is kind of an odd question. Since I usually develop applications
i usually develop for iPhone. But now trying to make a pong game in
Usually when I need to fork in C, I do something like this: pid_t
I plan to develop a nice little application that will run on an arm-based
I recently started working on a small CMS. I usually develop .NET applications in

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.