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

Add log and graph current branch #1163

Merged
merged 1 commit into from
Sep 12, 2019
Merged

Add log and graph current branch #1163

merged 1 commit into from
Sep 12, 2019

Conversation

stoivo
Copy link
Member

@stoivo stoivo commented Sep 11, 2019

#1150 (comment)

Hotfixes should be submitted to master branch. As part of the PR process,
you will be asked to provide the information necessary to make that happen.

Pull requests on new features should be submitted to dev branch and will be
regularly merged into master after evaluations over an extended period of
time.

Default.sublime-commands Outdated Show resolved Hide resolved
Default.sublime-commands Outdated Show resolved Hide resolved
@kaste
Copy link
Collaborator

kaste commented Sep 12, 2019

Hooray, we're green ✔️

@randy3k randy3k merged commit 9e1cf30 into dev Sep 12, 2019
@randy3k randy3k deleted the log_current_branch branch September 12, 2019 09:53
@kaste
Copy link
Collaborator

kaste commented Sep 25, 2019

A note: Adding more commands is also a bit problematic, bc you can't easily overwrite those with custom commands. Afaik when a user now adds a command with the same caption they appear twice. E.g. I want to have something like 'log current branch' to actually show only the commits from the tip to the merge-base. I already have a few custom commands, and it's an unsolved question how we can make GitSavvy hackable and customizable for its users.

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

Successfully merging this pull request may close these issues.

None yet

3 participants