Bugfix: Force binary rebuild
We need to rebuild the binary whenever the plugin has changed. Previously we were not doing this if the binary already existed. This MR adds an override parameter to the build() function which will force a rebuild even if the binary already exists. The README has been updated to note that this parameter should be used for Packer/Lazy, and when someone is troubleshooting. It won't be passed in to the build function during the normal setup call. Should address #55
This commit is contained in:
@@ -40,7 +40,7 @@ return {
|
||||
"stevearc/dressing.nvim", -- Recommended but not required. Better UI for pickers.
|
||||
enabled = true,
|
||||
},
|
||||
build = function () require("gitlab.server").build() end, -- Builds the Go binary
|
||||
build = function () require("gitlab.server").build(true) end, -- Builds the Go binary
|
||||
config = function()
|
||||
require("gitlab").setup()
|
||||
end,
|
||||
@@ -56,7 +56,7 @@ use {
|
||||
"MunifTanjim/nui.nvim",
|
||||
"nvim-lua/plenary.nvim"
|
||||
},
|
||||
run = function() require("gitlab.server").build() end,
|
||||
run = function() require("gitlab.server").build(true) end,
|
||||
config = function()
|
||||
require("gitlab").setup()
|
||||
end,
|
||||
@@ -244,7 +244,7 @@ vim.keymap.set("n", "<leader>glp", gitlab.pipeline)
|
||||
This plugin uses a Golang server to reach out to Gitlab. It's possible that something is going wrong when starting that server or connecting with Gitlab. The Golang server runs outside of Neovim, and can be interacted with directly in order to troubleshoot. To start the server, check out your feature branch and run these commands:
|
||||
|
||||
```
|
||||
:lua require("gitlab.server").build()
|
||||
:lua require("gitlab.server").build(true)
|
||||
:lua require("gitlab.server").start(function() print("Server started") end)
|
||||
```
|
||||
|
||||
|
||||
Reference in New Issue
Block a user