-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Update the badges of golangci-lint and homebrew in README.md
#4807
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
Merged
stefanhaller
merged 4 commits into
jesseduffield:master
from
kyu08:update-readme-golangci
Aug 11, 2025
Merged
Update the badges of golangci-lint and homebrew in README.md
#4807
stefanhaller
merged 4 commits into
jesseduffield:master
from
kyu08:update-readme-golangci
Aug 11, 2025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The old link was broken, it would have to be "Formula/l/lazygit.rb" instead of "Formula/lazygit.rb". However, I don't find it very useful to link to the raw formula file, so I decided to change the link to point to the homebrew web page for lazygit.
It doesn't really seem to make a difference, but this is what I get from shields.io's builder (no idea where the previous .svg extension came from).
053df0f to
8a7e42b
Compare
Both of these badges have the coloring logic to show stable releases in blue, and prereleases in orange. The criterion for a prerelease is that the major version is 0. Now it is debatable whether we consider lazygit "stable", but I don't feel we are in a preliminary state of the project, working towards the first final 1.0 release, so I feel blue expresses the state of the project better.
8a7e42b to
9850137
Compare
Collaborator
|
Thanks! LGTM. I added a few more commits to fix the badges for github version and homebrew, if you want to have a look before I merge. |
Contributor
Author
|
@stefanhaller I read your all the commit message, and totally agree with your changes and the rationale behind them. 👍 |
README.mdREADME.md
tmeijn
pushed a commit
to tmeijn/dotfiles
that referenced
this pull request
Aug 12, 2025
This MR contains the following updates: | Package | Update | Change | |---|---|---| | [jesseduffield/lazygit](https://github.com/jesseduffield/lazygit) | patch | `v0.54.1` -> `v0.54.2` | MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot). **Proposed changes to behavior should be submitted there as MRs.** --- ### Release Notes <details> <summary>jesseduffield/lazygit (jesseduffield/lazygit)</summary> ### [`v0.54.2`](https://github.com/jesseduffield/lazygit/releases/tag/v0.54.2) [Compare Source](jesseduffield/lazygit@v0.54.1...v0.54.2) <!-- Release notes generated using configuration in .github/release.yml at v0.54.2 --> Here's another point release; this one fixes a performance regression in 0.54.0 that made flicking through diffs a little less snappy (or a lot less, in some scenarios) than it could be. For the changes in 0.54.0, see https://github.com/jesseduffield/lazygit/releases/tag/v0.54.0. #### What's Changed ##### Fixes 🔧 - Fix scrollbar in certain popup panels (e.g. the intro message for new users) by [@​stefanhaller](https://github.com/stefanhaller) in jesseduffield/lazygit#4804 - Fix delay with flicking through files or commits when git diff is very slow by [@​stefanhaller](https://github.com/stefanhaller) in jesseduffield/lazygit#4803 ##### Maintenance ⚙️ - Stop bumping our homebrew formula by [@​stefanhaller](https://github.com/stefanhaller) in jesseduffield/lazygit#4799 - Update the badges of golangci-lint and homebrew in `README.md` by [@​kyu08](https://github.com/kyu08) in jesseduffield/lazygit#4807 ##### Docs 📖 - Fix the useHunkModeInStagingView hint in the breaking changes message by [@​stefanhaller](https://github.com/stefanhaller) in jesseduffield/lazygit#4800 - Update `CONTRIBUTING.md` to clarify translation contribution process by [@​kyu08](https://github.com/kyu08) in jesseduffield/lazygit#4806 **Full Changelog**: jesseduffield/lazygit@v0.54.1...v0.54.2 </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever MR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this MR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS42MS4xIiwidXBkYXRlZEluVmVyIjoiNDEuNjEuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiUmVub3ZhdGUgQm90Il19-->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Description
Now, the link of the badge of golangci-lint in
README.mdis expired. So I fixed it.PR Description
Now, the link of the badge of golangci-lint in
README.mdis expired. So I fixed it.[](https://golangci.com)[](https://golangci-lint.run/)Please check if the PR fulfills these requirements
Cheatsheets are up-to-date (rungo 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)