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

Define an user main branch #9

Open
mdbs99 opened this Issue Aug 5, 2017 · 4 comments

Comments

Projects
None yet
2 participants
@mdbs99
Owner

mdbs99 commented Aug 5, 2017

Let's give a possibility to user could define its own main branch (default is master).
Sometimes we could not push our changes into the main branch because this could be dangerous. So, because that, the user could define its own main branch.

This parameter should be stored in .gitconfig file with an option to user choose globally or not.

This main branch will be used in done, push, and release commands.

@mdbs99

This comment has been minimized.

Show comment
Hide comment
@mdbs99

mdbs99 Aug 5, 2017

Owner

It's better using git config instead create a new command.

So, these are the commands:

  • set info: git config git-work."branch".master master
  • get info: git config --get git-work.branch.master

This should be part of git-work.sh install as per #6.

Owner

mdbs99 commented Aug 5, 2017

It's better using git config instead create a new command.

So, these are the commands:

  • set info: git config git-work."branch".master master
  • get info: git config --get git-work.branch.master

This should be part of git-work.sh install as per #6.

@mdbs99

This comment has been minimized.

Show comment
Hide comment
@mdbs99

mdbs99 Aug 5, 2017

Owner

Well, maybe we can give to users just a command to set the main branch when them want like this:
git work config branch.master mybranch

Owner

mdbs99 commented Aug 5, 2017

Well, maybe we can give to users just a command to set the main branch when them want like this:
git work config branch.master mybranch

@mdbs99 mdbs99 added the @mdbs99 label Aug 6, 2017

@fabriciofx

This comment has been minimized.

Show comment
Hide comment
@fabriciofx

fabriciofx Aug 6, 2017

Collaborator

@mdbs99 To fix this issue, I need you merge PR #3 first.

Collaborator

fabriciofx commented Aug 6, 2017

@mdbs99 To fix this issue, I need you merge PR #3 first.

@mdbs99

This comment has been minimized.

Show comment
Hide comment
@mdbs99

mdbs99 Aug 7, 2017

Owner

@fabriciofx don't worry about this issue. When PR #3 is merged, I may do this issue.
Please, give attention in #10.

Owner

mdbs99 commented Aug 7, 2017

@fabriciofx don't worry about this issue. When PR #3 is merged, I may do this issue.
Please, give attention in #10.

mdbs99 added a commit that referenced this issue Aug 7, 2017

@mdbs99 mdbs99 referenced this issue Aug 8, 2017

Open

git work config #17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment