You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This makes the popups in the plugin (those for editing and creating comments, replies, the pipeline, etc) configurable. Users can change the default width, height, transparency, and border properties, and set overrides per popup.
Copy file name to clipboardExpand all lines: .github/CONTRIBUTING.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ If you are using Lazy as a plugin manager, the easiest way to work on changes is
20
20
build=function()
21
21
require("gitlab.server").build()
22
22
end,
23
-
dir="~/.path/to/your-closed-version", -- Pass in the path to your cloned repository
23
+
dir="~/.path/to/your-cloned-version", -- Pass in the path to your cloned repository
24
24
config=function()
25
25
require("gitlab").setup({})
26
26
end,
@@ -31,18 +31,18 @@ If you are making changes to the Go codebase, don't forget to run `make compile`
31
31
32
32
3. Apply formatters and linters to your changes
33
33
34
-
For changes to the Go codbase: We use <ahref="https://pkg.go.dev/cmd/gofmt">gofmt</a> to check formatting and <ahref="https://github.com/golangci/golangci-lint">golangci-lint</a> to check linting. Run these commands in the root of the repository:
34
+
For changes to the Go codebase: We use <ahref="https://pkg.go.dev/cmd/gofmt">gofmt</a> to check formatting and <ahref="https://github.com/golangci/golangci-lint">golangci-lint</a> to check linting. Run these commands in the root of the repository:
35
35
36
36
```bash
37
-
$ stylua .
38
-
$ luacheck --globals vim busted --no-max-line-length -- .
37
+
$ go fmt ./...
38
+
$ golangci-lint run
39
39
```
40
40
41
41
For changes to the Lua codebase: We use <ahref="https://github.com/JohnnyMorganz/StyLua">stylua</a> for formatting and <ahref="https://github.com/mpeterv/luacheck">luacheck</a> for linting. Run these commands in the root of the repository:
42
42
43
43
```bash
44
-
$ go fmt ./...
45
-
$ golangci-lint run
44
+
$ stylua .
45
+
$ luacheck --globals vim busted --no-max-line-length -- .
46
46
```
47
47
48
48
4. Make the merge request to the `main` branch of `.gitlab.nvim`
discussion_tree= { -- The discussion tree that holds all comments
125
135
blacklist= {}, -- List of usernames to remove from tree (bots, CI, etc)
@@ -252,7 +262,7 @@ To display all discussions for the current MR, use the `toggle_discussions` acti
252
262
require("gitlab").toggle_discussions()
253
263
```
254
264
255
-
You can jump to the comment's location in the reviewer window by using the `state.settings.discussion_tree.jump_to_reviewer` key, or the actual file with the 'state.settings.discussion_tree.jump_to_file' key.
265
+
You can jump to the comment's location in the reviewer window by using the `state.settings.discussion_tree.jump_to_reviewer` key, or to the actual file with the `state.settings.discussion_tree.jump_to_file` key.
256
266
257
267
Within the discussion tree, you can delete/edit/reply to comments with the `state.settings.discussion_tree.SOME_ACTION` keybindings.
By default when reviewing files you will see signs and diagnostics (if enabled in configuration). When cursor is on diagnostic line you can view discussion thread by using `vim.diagnostic.show`. You can also jump to discussion tree where you can reply, edit or delete discussion.
277
+
By default when reviewing files you will see signs and diagnostics (if enabled in configuration). When cursor is on diagnostic line you can view discussion thread by using `vim.diagnostic.show`. You can also jump to discussion tree where you can reply, edit or delete discussion.
The `discussion_sign` configuration controls the display of signs for discussions in the reviewer pane. Keep in mind that the highlights provided here can be overridden by other highlights (for example from diffview.nvim). This allows users to jump to comments in the current buffer in the reviewer pane directly.
283
+
The `discussion_sign` configuration controls the display of signs for discussions in the reviewer pane. This allows users to jump to comments in the current buffer in the reviewer pane directly. Keep in mind that the highlights provided here can be overridden by other highlights (for example from `diffview.nvim`).
274
284
275
-
These diagnostics are configurable in the same way that diagnostics are typically configurable in Neovim. For instance, the `severity` key sets the diagnostic severity level and should be set to one of `vim.diagnostic.severity.ERROR`, `vim.diagnostic.severity.WARN`, `vim.diagnostic.severity.INFO`, or `vim.diagnostic.severity.HINT`. The `display_opts` option configures the diagnostic display options where you can configure values like (this is directly used as opts in vim.diagnostic.set):
285
+
These diagnostics are configurable in the same way that diagnostics are typically configurable in Neovim. For instance, the `severity` key sets the diagnostic severity level and should be set to one of `vim.diagnostic.severity.ERROR`, `vim.diagnostic.severity.WARN`, `vim.diagnostic.severity.INFO`, or `vim.diagnostic.severity.HINT`. The `display_opts` option configures the diagnostic display options (this is directly used as opts in vim.diagnostic.set). Here you can configure values like:
276
286
277
287
-`virtual_text` - Show virtual text for diagnostics.
278
288
-`underline` - Underline text for diagnostics.
279
289
280
-
Diagnostics for discussions use the `gitlab_discussion` namespace. See `:h vim.diagnostic.config` and `:h diagnostic-structure` for more details. Signs and diagnostics have common settings in `discussion_sign_and_diagnostics`. This allows customizing if discussions that are resolved or no longer relevant should still display visual indicators in the editor. The `skip_resolved_discussion` Boolean will control visibility of resolved discussions, and `skip_old_revision_discussion` whether to show signs and diagnostics for discussions on outdated diff revisions.
290
+
Diagnostics for discussions use the `gitlab_discussion` namespace. See `:h vim.diagnostic.config` and `:h diagnostic-structure` for more details. Signs and diagnostics have common settings in `discussion_sign_and_diagnostic`. This allows customizing if discussions that are resolved or no longer relevant should still display visual indicators in the editor. The `skip_resolved_discussion` Boolean will control visibility of resolved discussions, and `skip_old_revision_discussion` whether to show signs and diagnostics for discussions on outdated diff revisions.
281
291
282
292
When interacting with multiline comments, the cursor must be on the "main" line of diagnostic, where the `discussion_sign.text` is shown, otherwise `vim.diagnostic.show` and `jump_to_discussion_tree_from_diagnostic` will not work.
283
293
284
294
### Uploading Files
285
295
286
-
To attach a file to an MR description, reply, comment, and so forth use the `settings.popup.perform_linewise_action` keybinding when the popup is open. This will open a picker that will look in the directory you specify in the `settings.attachment_dir` folder (this must be an absolute path) for files.
296
+
To attach a file to an MR description, reply, comment, and so forth use the `settings.popup.perform_linewise_action` keybinding when the popup is open. This will open a picker that will look for files in the directory you specify in the `settings.attachment_dir` folder (this must be an absolute path).
287
297
288
298
When you have picked the file, it will be added to the current buffer at the current line.
289
299
@@ -331,8 +341,7 @@ require("dressing").setup({
331
341
332
342
### Restarting or Shutting Down
333
343
334
-
The `gitlab.nvim` server will shut down automatically when you exit Neovim. However, if you would like to manage this yourself (for instance, restart the server when you check out a new branch) you may do so via the `restart` command, or `shutdown` commands, which
335
-
both accept callbacks.
344
+
The `gitlab.nvim` server will shut down automatically when you exit Neovim. However, if you would like to manage this yourself (for instance, restart the server when you check out a new branch) you may do so via the `restart` command, or `shutdown` commands, which both accept callbacks.
**To check that the current settings of the plugin are configured correctly, please run: `:lua require("gitlab").print_settings()`**
384
393
385
-
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:
394
+
This plugin uses a Go server to reach out to Gitlab. It's possible that something is going wrong when starting that server or connecting with Gitlab. The Go 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:
0 commit comments