Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unneeded branches/Update on branches #13

Open
luckyx1 opened this issue Jun 22, 2014 · 2 comments
Open

Unneeded branches/Update on branches #13

luckyx1 opened this issue Jun 22, 2014 · 2 comments
Labels

Comments

@luckyx1
Copy link
Contributor

luckyx1 commented Jun 22, 2014

feature/AF-page-sequence & feature/initial-login haven't been used in a long time
features/DCC/seed-remaning-model & features/scaffold-condition has already been slurped into master and is just hanging there.

I would like to propose as so that we can keep the branches clean and modularize that every team has a branch push to master of their current work, as mention before in Armando's email either as features/Name(or group separated /)-task
or bug/etc to know what you are currently working on. Once you are done with that branch, please remove it before 50 more branches will be on this. Thank you for reading.
Robert & Steven

@armandofox
Copy link
Contributor

good point. i'll delete my unused branches.
Armando Fox
Professor, Computer Science Division
Faculty Advisor, UC Berkeley MOOCLab
fox .at. cs .dot. berkeley .dot. edu
581 Soda Hall MC#1776, Berkeley, CA 94720-1776
+1.510.642.6820 / http://www.cs.berkeley.edu/~fox

TAKE MY CLASS FOR FREE VIA edX: http://saas-class.org
LIKE IT ON FACEBOOK: http://facebook.com/saas-class
TRY MY BOOK (NOT FREE): http://beta.saasbook.info (goes with the course)

On Jun 22, 2014, at 12:36 PM, Robert Hernandez notifications@github.com wrote:

feature/AF-page-sequence & feature/initial-login haven't been used in a long time
features/DCC/seed-remaning-model & features/scaffold-condition has already been slurped into master and is just hanging there.

I would like to propose as so that we can keep the branches clean and modularize that every team has a branch push to master of their current work, as mention before in Armando's email either as features/Name(or group separated /)-task
or bug/etc to know what you are currently working on. Once you are done with that branch, please remove it before 50 more branches will be on this. Thank you for reading.
Robert & Steven


Reply to this email directly or view it on GitHub.

@chiaracoetzee
Copy link

It took me a while to figure out how to do it. Just to check this is the syntax I used:

git push origin :features/DCC/seed-remaining-models
git push origin :features/scaffold-condition

These were my branches and I think they're gone now. I haven't worked with feature-per-branch workflow or git branches before so I'm pretty new to all this. Hopefully the deleted information is still archived somewhere in case it's needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants