Turn The Branchs To Be Folders Of Master?
I have a repo in Github.
repo: - master - a - b
I want to turn the branches(a, b) to be folders behind the
master/b and delete
I get the impression that you're misunderstanding how branches work. Check out this interactive tutorial which shows you what happens realistically when you branch off of master.
Now, for some verbal explanation:
- The likely case is that each of your branches is already a child off of a commit from master.
- There is no need to subclass your branch names underneath master, nor can you - you'd get an error that says something like,
fatal: cannot lock ref 'refs/heads/master/foo': 'refs/heads/master' exists; cannot create 'refs/heads/master/foo'.
- You can, however, name your branches similar to folders, so you could have
hotfixes/release/18, for example.
- You should stick to the basic convention of naming your branches after what they represent. If you need to figure out where it came from, you can use
git log --graph --oneline --decorateto figure out where it came from originally.
- → Authenticate with a cookie using laravel 5.1 and jwt
- → Finding a specific GitLab tag from PHP
- → React: How to publish page on server using React-starter-kit
- → babel-loader, webpack, ES2015 modules: "Element type is invalid"
- → Create a function-attribute of a function, which is, in its turn, a method of an object literal
- → Model Validation in laravel 5.1 not working
- → GIT fatal: loose object
- → Laravel validation required rule not working
- → Axios array map callback
- → Where does this `webpack://` come from for `webpack-dev-middleware`?
- → error when trying to modify project in laravel forge
- → GitHub Pages and Jekyll content duplication and SEO issues
- → Use Laravel repositories with Datatables