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 vision and design principles doc #4053

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add vision and design principles doc #4053

wants to merge 1 commit into from

Conversation

jesseduffield
Copy link
Owner

I want to spell out the design principles behind Lazygit so that our priorities are clear and it's easier to make UX decisions (especially for early contributors).

It's not possible to codify this in a way that will resolve all disputes but I think it's worthwhile to enumerate some of the things that keep coming up in our discussions about X or Y feature.

This is a very rough draft (effectively a brain-dump). So I expect plenty of feedback :)

CC @stefanhaller @karimkhaleel @mark2185 @afhoffman @AzraelSec

  • Please check if the PR fulfills these requirements
  • Docs have been updated if necessary

I want to spell out the design principles behind lazygit so that our priorities are clear
and it's easier to make UX decisions
Copy link

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation Diff coverage
Report missing for b0a766c1
Coverage variation details
Coverable lines Covered lines Coverage
Common ancestor commit (b0a766c) Report Missing Report Missing Report Missing
Head commit (77c1b93) 50681 43629 86.09%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details
Coverable lines Covered lines Diff coverage
Pull request (#4053) 0 0 ∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more

Footnotes

  1. Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.

- Safety
- Power
- Speed
- Comformity with git
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Comformity with git
- Conformity with git

@karimkhaleel
Copy link
Contributor

karimkhaleel commented Nov 9, 2024

Document how to solve various git problems with Lazygit

Strongly agree with this point. Too often I see people struggling with their repos because they are not even aware of many of the ways you can manipulate commits and branches. I really like how Lazygit allows Git's features to be very easily accessible and not behind a completely opaque UI (i.e you can see exactly what git commands are running in the background).

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

Successfully merging this pull request may close these issues.

2 participants