Skip to content

reword documentation for git.autoForwardBranches #4545

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

Conversation

sean-xyz
Copy link
Contributor

@sean-xyz sean-xyz commented May 8, 2025

  • PR Description

The wording "lazygit will automatically forward branches to their upstream after fetching" could be interpreted to mean that lazygit automatically pushes branches, rather than operating locally. Edited to make the behavior more clear.

  • Please check if the PR fulfills these requirements
  • Cheatsheets are up-to-date (run go generate ./...)
  • Code has been formatted (see here)
  • Tests have been added/updated (see here for the integration test guide)
  • Text is internationalised (see here)
  • If a new UserConfig entry was added, make sure it can be hot-reloaded (see here)
  • Docs have been updated if necessary
  • You've read through your own file changes for silly mistakes etc

@stefanhaller
Copy link
Collaborator

Makes sense, thanks.

@stefanhaller stefanhaller merged commit ef1da6f into jesseduffield:master May 9, 2025
26 of 27 checks passed
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